Backbone alert settings

You can create test level and step level alerts for Backbone tests. These alert types are available:

Default values for new alerts are defined in the Test Defaults.

You can't create alerts as part of provisioning a new test. After the test is created, open the editing page for the test to define the alerts.

Configuring test level alerts

  1. In the Edit a Backbone Test page, select the Test Level Alerts tab.
  2. Response Time Alerts is selected by default. To select a different alert, scroll to the bottom of the page and click the alert type.
  3. Configure the alert settings as described below.
  4. Add notifications as described below.
  5. Click Update to save the settings and continue editing the test, or Update and Finish to save the settings and return to the Tests page.

Configuring step level alerts

  1. Select the Step Level Alerts tab.
  2. Select the step to configure.
    The test's first step is selected by default.
  3. Response Time Alerts is selected by default. Click Transaction Failure Alerts to configure that alert type.
  4. Configure the alert settings as described below.
  5. Add notifications as described below.
  6. Click Update to save the settings and continue editing the test, or Update and Finish to save the settings and return to the Tests page.

Alert settings

Response Time alerts

Activation

Select On to enable the alert, or Off to disable it.

Test Thresholds for Error Conditions

Select either a dynamic or static threshold, then specify the warning and severe levels.

Node Thresholds

Enter either the minimum Percent of Nodes or the minimum Number of Nodes where the error must occur before an alert is triggered.

Number of consecutive errors

For a test level alert, select the minimum number of consecutive errors that trigger an alert.

This setting is not available for step level alerts.

Back to Configuring Test Level Alerts or Configuring Step Level Alerts

Transaction Failure alerts

Activation

Select to On to enable the alert, or Off to disable it.

Retry on Error

Select On to enable Retry on Error. It is Off by default.

When Retry on Error is enabled, network, socket and SSL errors (10xxx, 11xxx, 12xxx, 15000 and 18001 errors) will trigger immediate re-execution of the test:

  • If the re-execution also fails, the test will be recorded as a failure and will trigger an alert.
  • If the re-execution is successful, only the successful result is saved, to reduce false alerts and improve overall availability (taking account of transient issues such as network connectivity).

Best practice is to enable Retry on Error in all Transaction Failure Alerts for Backbone tests.

When using Retry on Error with single-URL tests, there is no charge for the initial failed test. For multi-step tests, there is no charge for the first page of the failed test, but you will be charged for additional steps in the failed test.

For example, you have a 5-step test that fails on Step 3. During the retry, all 5 steps run successfully. You will be charged for (3-1)+5=7 steps.

Node Thresholds

Enter either the minimum Percent of Nodes or the minimum Number of Nodes that must experience the error to trigger an alert.

Number of consecutive errors

For a test level alert, select the minimum number of consecutive errors that trigger an alert.

This setting is not available for step level alerts.

Back to Configuring Test Level Alerts or Configuring Step Level Alerts

Object Failure alerts

Activation

Select to On to enable the alert, or Off to disable it.

Test Threshold

Enter either the minimum Percent of Objects or the minimum Number of Objects that must have errors to trigger an alert.

Node Thresholds

Enter either the minimum Percent of Nodes or the minimum Number of Nodes that must experience the error to trigger an alert.

Number of consecutive errors

Select the minimum number of consecutive errors that trigger an alert.

Include Object Level Detail

Select whether to include a list of objects and failed objects in the alert details. When you select this setting, an attachment with this information is included in an alert email.

Back to Configuring Test Level Alerts or Configuring Step Level Alerts

Byte Limit alerts

Activation

Select to On to enable the alert, or Off to disable it.

Test Threshold

Enter the lower and upper byte limits. The alert is triggered if the bytes loaded for the completed page total less than the lower limit or more than the upper limit.

Node Thresholds

Enter either the minimum Percent of Nodes or the minimum Number of Nodes that must experience the error to trigger an alert.

Number of consecutive errors

Select the minimum number of consecutive errors that trigger an alert.

Back to Configuring Test Level Alerts or Configuring Step Level Alerts

Notifications

Use the Notifications section of the alert settings to specify who should be notified of the alert, and whether reminders should be sent until the test returns to "Good" status.

Use these options to help you determine where to send alert notifications:

All alerts are sent to the Alert log besides being sent to the selected destinations.

You can define as many notifications as needed for the people who need to be notified when the alert is triggered. Repeat these steps for each notification:

  1. Click Add Notification to display the configuration fields.

  2. Select the Level of notification to configure. The level options depend on the alert type.

    • Response Time – Improved, Warning, Severe
    • Transaction Failure – Improved, Failed
    • Object Failure – Improved, Failed
    • Byte Limit – Improved, Failed
  3. Select the destination for this alert.
    The Destination list includes all alert destinations defined for your account.
    You can also select the built-in destination mobile application (push notification) to send notifications to a mobile device through the Dynatrace Synthetic Mobile app.

  4. When you select an email destination, the subject line for that destination appears in the field below the alert destination. You can modify the subject line for this notification. For more information about defining the subject line, see Alert Destinations.

  5. To send reminders, select Send Reminders, then select a frequency from the Reminders Frequency list. The default setting is never (don't send any reminders).

    • Reminders can only be sent to an alert destination; they cannot be sent if no destination (alert log only) is selected.
    • Reminders cannot be sent to an integration destination (ServiceNow, Slack, or VictorOps).
    • Reminders cannot be sent for Improved alerts.
    • Reminders will be sent until the test returns to "Good" status. Set the reminder so that at least one test run can occur before a reminder would be sent. For example, if the test frequency is every 15 minutes and the reminder frequency is only 5 minutes, reminders will be sent before the next test run shows whether the test is still in an alert status or has improved.
  6. Click Update to save the notification, or Update and Finish if you have completed all edits.

To stop sending notifcations to a destination, select no destination (alert log only) in the Destination/Subject list for the destination.

Back to Configuring Test Level Alerts or to Configuring Step Level Alerts