Get Pingdom style alert notifications

Get Pingdom style notifications for your website, URI, and Synthetic transaction entities in SolarWinds Observability. For example, if you are using SolarWinds Observability to monitor your website entity's availability, you can configure Pingdom style notifications that trigger when your website, is down.

Use the Website down, URI down, or Synthetic transaction down alerts from Alert Templates, or configure the alert from scratch using the state.nativeState attribute.

The Digital Experience down alert templates use the state.nativeState attribute to alert you once your website, URI, or Synthetic transaction is in the down state. This alert can be sent to email configurations within SolarWinds Observability and other email addresses. This includes the default Digital Experience alert templates and supports system-generated Atlassian Status page email addresses.

Create a Pingdom style website down alert for monitored websites with the Template

Open Alert Settings and click the Templates tab.
Search for website templates.
Click the vertical ellipsis on the website down template, and then click Create Alert.
Review the Details page. Modify the alert name, description, severity, and enable alert setting. Optional: Enter a Runbook URL. Click Next.
Review the Alert Type page. Metric Condition is selected in the template by default. Click Next.
Review the settings on the Conditions page. The website down template is configured to alert you when the state.nativeState of any monitored website entity is down. You can keep this configuration, or refine the scope to trigger only for selected websites.
Configure the alert scope and condition:
1. Entity type: The Website entity type is selected by default.
2. Scope by: All is selected by default.
3. Alert Condition: state.nativeState == down is selected by default.
4. Click Next.
Add email notification(s):
1. Click Add.
2. Select Email from the Services drop-down.
3. Select an existing email configuration, or click Add a New Configuration.
4. Set the resend frequency in minutes or seconds.
5. Repeat these steps for any additional emails you want to alert.
6. Optional: Click the Send an attentional notification toggle to be alerted once the alert is cleared.
7. Click Next.
Review the Create Alert Summary. Click Create to complete your website down alert.

Create a Pingdom style URI down alert for URI entities with the template

Open Alert Settings and click the Templates tab.
Search for website templates.
Click the vertical ellipsis on the URI down template, and then click Create Alert.
Review the Details page. Modify the alert name, description, severity, and enable alert setting. Optional: Enter a Runbook URL. Click Next.
Review the Alert Type page. Metric Condition is selected in the template by default. Click Next.
Review the settings on the Conditions page. The URI down template is configured to alert you when the state.nativeState of any monitored URI entity is down. You can keep this configuration, or refine the scope to trigger only for selected URIs.
Configure the alert scope and condition:
1. Entity type: The URI entity type is selected by default.
2. Scope by: All is selected by default.
3. Alert Condition: state.nativeState == down is selected by default.
4. Click Next.
Add email notification(s):
1. Click Add.
2. Select Email from the Services drop-down.
3. Select an existing email configuration, or click Add a New Configuration.
4. Set the resend frequency in minutes or seconds.
5. Repeat these steps for any additional emails you want to alert.
6. Optional: Click the Send an attentional notification toggle to be alerted once the alert is cleared.
7. Click Next.
Review the Create Alert Summary. Click Create to complete your URI down alert.

Create a Pingdom style Synthetic Transaction down alert with the template

Open Alert Settings and click the Templates tab.
Search for website templates.
Click the vertical ellipsis on the Synthetic Transaction down template, and then click Create Alert.
Review the Details page. Modify the alert name, description, severity, and enable alert setting. Optional: Enter a Runbook URL. Click Next.
Review the Alert Type page. Metric Condition is selected in the template by default. Click Next.
Review the settings on the Conditions page. The Synthetic Transaction down template is configured to alert you when the state.nativeState of any monitored Synthetic transaction entity is down. You can keep this configuration, or refine the scope to trigger only for selected Synthetic transactions.
Configure the alert scope and condition:
1. Entity type: The Synthetic transaction entity type is selected by default.
2. Scope by: All is selected by default.
3. Alert Condition: state.nativeState == down is selected by default.
4. Click Next.
Add email notification(s):
1. Click Add.
2. Select Email from the Services drop-down.
3. Select an existing email configuration, or click Add a New Configuration.
4. Set the resend frequency in minutes or seconds.
5. Repeat these steps for any additional emails you want to alert.
6. Optional: Click the Send an attentional notification toggle to be alerted once the alert is cleared.
7. Click Next.
Review the Create Alert Summary. Click Create to complete your Synthetic Transaction down alert.

Add SMS notifications to your alert

SMS notifications are only supported for Digital Experience entities (websites, URIs, and synthetic transaction entities) when alerts are configured with the state.nativeState attribute. This feature is only available for paid plans.

For information on SMS pricing, see the Subscription topic.

Create a metric condition alert definition for the state.nativeState attribute for one of the following entities.
1. Website
2. URI
3. Synththetic transaction.
Continue to the Actions step on the Create Alert or Edit Alert wizard.
Under the Services drop-down click SMS.
Select an existing SMS configuration, or click + Add a new configuration.
Complete the Create SMS Configuration:
1. Enter a name for your SMS recipient.
2. Enter a description for your SMS recipient.
3. Select a notification timezone from the drop-down menu.
4. Enter the phone number. Click Add to add the phone number.
5. Click Notification Test to send a test notification to your phone number.
  
  The notification test counts toward your SMS quota. In case of a test failure, the Test notification result box appears, providing details.
6. Click Create to save your changes.

Notify external recipients through email

External recipients can receive email notifications only when the default templates are used. You can't add external recipients to alerts created with a custom template.

You can add external recipients to alert notifications on the Actions step of the Create Alert or Edit Alert wizards. You can also add external recipients through notification services.

Add an external recipient through the alert wizard

Navigate to the Actions step on the Create Alert or Edit Alert wizard.
Under the Services drop-down click Email.
Under the Configurations drop-down, click + Add a new configuration.
Complete the Create Email Configuration:
1. Enter a name for your external recipient.
2. Enter a description for your external recipient.
3. Select a notification timezone from the drop-down menu.
4. Enter the external email. Click Add (email name) to add the email.
5. Click Notification Test to send a test notification to your external email.
6. Click Create to save your changes.

Add an external recipient through notification services

Click Settings > Notification Services.
Click Email.
Click Create Configuration.
Complete the Create Email Configuration:
1. Enter a name for your external recipient.
2. Enter a description for your external recipient.
3. Select a notification timezone from the drop-down menu.
4. Enter the external email. Click Add (email name) to add the email.
5. Click Notification Test to send a test notification to your external email.
6. Click Create to save your changes.

Search SolarWinds Support