Exploring synthetic monitoring
Summarize
Summary of Exploring synthetic monitoring
Synthetic monitoring in ServiceNow enables proactive, automated testing of HTTP service endpoints by simulating user interactions. This approach helps identify bugs, performance issues, and outages before real users are affected. Synthetic monitors continuously test endpoints defined in the Configuration Management Database (CMDB), checking for availability, response times, and specific response content. Failed tests trigger alerts through Event Management, allowing early issue detection and resolution.
Show less
Tests can be executed from various locations including the ServiceNow platform (for publicly accessible endpoints), Agent Client Collectors (ACC), or MID Servers deployed in your network.
Roles and Responsibilities
- Synthetic monitoring administrator (admin role): Assigns roles, creates and edits monitors, and views test results.
- Service owner (Editor role): Creates and edits monitors, views test results, and manages alert configurations.
- Network operation center (NOC) operator (Viewer role): Monitors test outcomes and responds to alerts.
How Synthetic Monitoring Works
- Service owners select critical endpoints to monitor.
- Admins and service owners configure locations for running tests (default ServiceNow hosted location, ACC Proxy clusters, or MID Servers).
- Monitors are configured with criteria such as expected HTTP status codes and maximum response times.
- Tests run on the configured schedule, with results reviewed and alerts generated upon failure.
- Operators and service owners use results and alerts to maintain service health.
Benefits
- Comprehensive Monitoring: Access an aggregate view of all monitors and their statuses via the synthetic monitoring homepage.
- Detailed Insights: Review monitor configurations, test success rates, response times, historical logs, and alert listings.
- Proactive Alerts: Receive real-time notifications for outages or performance degradations before users are impacted.
- Customizable Monitoring: Edit and deactivate monitors to align with changing business requirements.
- Integration: Embed synthetic monitoring results within Service Observability dashboards for consolidated service health visibility.
Next Steps for ServiceNow Customers
To leverage synthetic monitoring effectively, customers should explore configuration and usage guides, including:
- Setting up synthetic monitors and locations
- Identifying system issues using synthetic monitoring data
- Utilizing the Synthetic Monitoring Developer Guide and APIs for advanced use cases
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 users 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.
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
Admins, service owners, and NOC operators use synthetic monitoring in the following way:
- As a service owner, you determine which endpoints to monitor based on business criticality.
- As an admin or service owner, you configure locations to run the monitor from.Note:The ServiceNow hosted location is available by default and does not have 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.
- 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.
- Synthetic monitoring runs tests based on the monitor's configuration and reports the results of each test.
- As a service owner or operator, you monitor the test results and also respond to any generated alerts.
Synthetic monitoring benefits
| Benefit | Feature | Users |
|---|---|---|
| View aggregate monitor information. View the synthetic monitoring home page where you can:
|
View aggregate information about the monitors. | Operators, service owners |
| Visualize synthetic test results. View the details page for a monitor where you can see:
|
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 |