Plugins 〉Synthetic Monitoring


Synthetic Monitoring

  • Overview
  • Installation
  • Change log
  • Related content

Synthetic monitoring application

Synthetic Monitoring is a blackbox monitoring solution provided as part of Grafana Cloud. Synthetic Monitoring provides users with insights into how their applications and services are behaving from an external point of view. Users can define checks to continually test remote targets from 1 or more probe locations around the world to assess the availability, performance and correctness of the services. As each check runs, metrics and logs are collected and published to the user's Grafana Cloud service. Metrics are published to Grafana Cloud Prometheus and logs are published to Grafana Cloud Loki.

Synthetic monitoring is the successor to the original worldping application. The refreshed Synthetic Monitoring product focuses on reducing complexity and taking advantage of Grafana Cloud capabilities.

Check Types

Users can define HTTP/HTTPS, DNS, TCP and ICMP Ping checks to monitor their remote targets. Internally, the Synthetic Monitoring solution uses the Prometheus Blackbox exporter for executing the checks and collecting metrics and logs. When creating a check, users are able to customize the settings and validation rules supported by the Blackbox exporter.

Probe Locations

For each check, users can select 1 or more 'public' probe locations distributed throughout the world to run tests from. Additionally, users can run their own 'private' probe locations by downloading and deploying the Synthetic Monitoring Agent.


Synthetic Monitoring requires a Grafana Cloud account, and is installed by default in Grafana Cloud stacks. A local Grafana instance can be configured to connect to Synthetic Monitoring via a provisioning file:

apiVersion: 1


  • type: grafana-synthetic-monitoring-app name: grafana-synthetic-monitoring-app disabled: false jsonData: apiHost: stackId: <instance ID of your hosted grafana> logs: grafanaName: <name of an existing Loki datasource pointing to the Grafana Cloud Loki instance> hostedId: <Grafana Cloud Loki instance ID> metrics: grafanaName: <name of an existing Prometheus datasource pointing to the Grafana Cloud Prometheus instance> hostedId: <Grafana Cloud Prometheus instance ID> secureJsonData: publisherToken: <metric publisher token from>

Note: you can add a provisioning block per org to provision the plugin for multiple orgs. You can provide different values for each org block and connect to a different cloud stack per org.

The names of the datasources specified in the provisioning file must match the names of existing datasources in Grafana. If you are also provisioning the datasources using the procedure below, make sure the datasource names match.


  1. A datasource pointed at a Prometheus instance hosted in Grafana Cloud
  2. A datasource pointed at a Loki instance hosted in Grafana Cloud

Note: The Prometheus and Loki instances must be part of the same Cloud stack

The required datasources can be added via provisioning. The information needed can be copied from Prometheus and Loki datasources found in the datasources tab of a Cloud hosted Grafana instance:

apiVersion: 1


  • name: <datasource name> type: loki access: proxy url: basicAuth: true basicAuthUser: <Grafana Cloud Loki instance ID> jsonData: maxLines: 1000 secureJsonData: basicAuthPassword: <viewer token from> version: 1

  • name: <datasource name> type: prometheus access: proxy url: basicAuth: true basicAuthUser: <Grafana Cloud Prometheus instance ID> jsonData: timeInterval: 1s secureJsonData: basicAuthPassword: <viewer token from> version: 1

To start the using app:

  1. Navigate to Synthetic Monitoring via the sidebar
  2. Click the Get Started button. This will initialize the app.

During the Initialization process, the Synthetic Monitoring backend will:

  1. Validate the Publisher API key provided in the provisioning file.
  2. Ensure the account has active Grafana Cloud Prometheus and Grafana Cloud Loki services
  3. The dashboards included with the App will then be imported.
  4. Finally, the Synthentic Monitoring Backend will be notified that the service is ready.

Users can then create checks to monitor their remote targets. Metrics and logs will flow into the selected Cloud stack.

For more information, visit the docs on plugin installation.

1.5.3 (2021-09-20)

Bug Fixes

  • Fix a dashboard config error

1.5.2 (2021-09-20)

Bug Fixes

  • make homepage usage breakpoints smaller (#367) (d157abe)

1.5.1 (2021-09-14)

Bug Fixes

  • config setup button was routing to a 404 (#365) (a08a9c8)

1.5.0 (2021-09-13)


1.4.0 (2021-09-08)


  • Add beta feature traceroute behind a feature flag (#245) (89ab9b1)

1.3.2 (2021-09-08)

Bug Fixes

  • check type selector should be disabled on edit (#360) (dda165e)

1.3.0 (2021-08-27)

Bug Fixes


  • almost there... skipping docs publish step (d97521c)
  • gcom token secret (1c2b5b8)

Change Log

[1.2.30] - 2021-08-27

  • New start to changelog with updated build process