Overview

You can use metrics generated from your Synthetic tests to create metric monitors in addition to the Synthetic monitor created with your test.

Example metric monitor that alerts when too many tests are failing in CI

With metric monitors, you can accomplish the following:

  • Monitor the total response time
  • Scope on specific HTTP timings such as DNS, the DNS resolution, and TCP connection
  • Access tags added to metrics coming from Synthetic tests

This guide demonstrates how to set up a metric monitor using a general metric such as synthetics.test_runs.

Create a metric monitor

Example metric monitor that alerts when too many tests are failing in CI
  1. To create a metric monitor, navigate to Monitors > New Monitor and click Metric.

  2. Select a detection method to customize your monitor’s alerting conditions. For this example, you can create a threshold alert metric monitor.

    Threshold Alert
    An alert is triggered whenever a metric crosses a threshold.
    Change Alert
    An alert is triggered when the delta between values is higher than the threshold.
    Anomaly Detection
    An alert is triggered whenever a metric deviates from an expected pattern.
    Outliers Alert
    An alert is triggered whenever one member in a group behaves differently from its peers.
    Forecast Alert
    An alert is triggered whenever a metric is forecast to cross a threshold in the future.
  3. In the Define the metric section, enter a Synthetic Monitoring metric such as synthetics.test_runs, where you can filter on status, response codes, and retry behavior.

  4. Set the alerting conditions and add a notification message.

  5. Set editing permissions and click Create.

Further Reading