Exploring synthetic monitoring

Learn how synthetic monitoring provides proactive, automated testing of service endpoints. By simulating user interactions, it can identify bugs, performance issues, and outages before they impact real users.

Synthetic monitoring overview

Synthetic monitors continually call HTTP endpoints in the Configuration Management Database (CMDB) to test availability, response times, or the presence of a defined string in the response body. When a test fails the configured criteria, it can alert you to endpoint issues before your customers do.

For example, you might create a monitor that tests the GET HTTP endpoint of a service. You could configure that monitor to check for a status code of 200 and a response time of under 500 ms. If any code other than 200 is returned or the request takes longer than 500 ms, the test fails. An alert can then be generated and sent through Event Management.

The synthetic monitoring tests can be run by an Agent Client Collector (ACC) deployed in your network, on a MID Server, or on the ServiceNow platform.

注:

The HTTP endpoints must exist in the HTTP Endpoints [cmdb_ci_endpoint_http] table. Endpoints tested from the ServiceNow platform must be publicly accessible.

Synthetic monitoring users

表 : 1. Synthetic monitoring users

User	Description
Synthetic monitoring administrator (Admin role)	Assigns roles, creates and edits monitors, and views monitor tests and their results.
Service owner (Editor role)	Creates and edits monitors and can also view monitor tests and their results.
Network operation center (NOC) operator (Viewer role)	Monitors tests and their results.

Synthetic monitoring customer-hosted workflow

図 : 1. Synthetic monitoring workflow

Admins, service owners, and NOC operators use synthetic monitoring in the following way:

1. As a service owner, you determine which endpoints to monitor based on business criticality.
2. As an admin or service owner, you configure locations to run the monitor from.
   注:

   The ServiceNow hosted location is available by default and doesn't need to be configured. However, endpoints tested by that location must be publicly available. You can also run the monitor from an ACC Proxy cluster or a MID Server.
3. As an admin or service owner, you configure the monitor and then after it runs once, review the results of the tests. If the results aren't successful, you troubleshoot the configuration. You can also create an alert that fires when a test fails.
4. Synthetic monitoring runs tests based on the monitor's configuration and reports the results of each test.
5. As a service owner or operator, you monitor the test results and also respond to any generated alerts.

Synthetic monitoring benefits

表 : 2. Synthetic monitoring benefits

Benefit	Feature	Users
View aggregate monitor information. View the synthetic monitoring home page where you can: See an aggregate view of all monitors View the status of all monitors. Drill down into a monitor's details	View aggregate information about the monitors.	Operators, service owners
Visualize synthetic test results. View the details page for a monitor where you can see: The status and configuration of the monitor. Charts that display test success and response time. A historical log of synthetic test runs, including details and the response body. A listing of alerts associated with the monitor.	View a monitor and its tests.	Operators, service owners
Get real-time notifications for outages before they impact users.	Optionally configure alerts when tests don't succeed.	Operators, service owners
Share insights with stakeholders.	View aggregate monitor information.	Operators, service owners
Update monitors to match your business needs.	Edit existing monitors, including deactivation.	Service owner
Embed monitor results in a Service Observability dashboard.	Use synthetic monitoring with Service Observability	Service owner

What to explore next

To learn more about configuring and using synthetic monitoring, see:

• Configuring synthetic monitoring
• Identifying system issues with synthetic monitoring
• Synthetic monitoring reference
• Use synthetic monitoring with Service Observability