Docs » Introduction to Splunk Synthetic Monitoring

Introduction to Splunk Synthetic Monitoring đź”—

Create detailed tests to proactively monitor the speed and reliability of websites, web apps, and resources over time, at any stage in the development cycle.

To keep up to date with changes in Synthetic Monitoring, see the Splunk Observability Cloud release notes.

How does Splunk Synthetic Monitoring work? đź”—

Synthetic tests are the primary mechanism of application monitoring in Splunk Synthetic Monitoring. You can set up Browser tests and Uptime tests to monitor various aspects of your site or application. You can set up these tests to run at your preferred frequency from the devices and locations of your choosing.

Each occurrence of a test from a particular device and location at a specific time is called a run. Each run of a test captures a set of metrics that provide insight into your application’s performance. See Browser test metrics. You can view this data at the per-run level, or you can view test-level aggregations that provide the data you need at a glance.

You can also set up alerts that notify you when tests fail and come back online. See Detectors and alerts.

Use cases for Splunk Synthetic Monitoring đź”—

You can use Splunk Synthetic Monitoring for the following use cases:

  • Proactively monitor site availability before it affects users

  • Report on the availability or impact of third-party services

  • Check how new code deployments improve or degrade performance

  • Test your site performance against competitors’ sites

  • Scan for moved or broken links on your site

To see an example of using Splunk Observability Cloud components together, see APM Scenarios .

Create your first test with Splunk Synthetic Monitoring đź”—

To create your first test with Splunk Synthetic Monitoring, see Set up Splunk Synthetic Monitoring.

This page was last updated on Sep 27, 2024.