Scale Your Monitoring. Close the Gaps. Do It Automatically.

[saraarntz]

Every unmonitored endpoint is a blind spot waiting to become an incident. This March, we're making it dramatically easier to eliminate those blind spots, whether you're migrating from another vendor, scaling thousands of monitors, or simply closing gaps faster when something goes wrong. Two new capabilities are now available in ServiceNow Synthetic monitoring. 

REST API for Monitor Management 

Whether you're running a large-scale migration from another monitoring tool or building monitoring directly into your deployment pipeline, our API integrates cleanly with how your team already works. You can now create, update, and manage synthetic monitors programmatically via our REST API, with full support for both JSON and CSV formats.  

Teams migrating from other vendors can import existing tests in bulk using CSV upload, eliminating the manual effort of recreating monitors one by one. For organizations scaling rapidly, the API makes it practical to deploy hundreds or thousands of monitors programmatically, keeping your monitoring footprint in step with your infrastructure without creating a bottleneck for the team managing it. 

The API also opens automation possibilities that weren't previously available. Monitor creation can now be wired into CI/CD pipelines, service catalog requests, or change management workflows, so new services get monitoring coverage as part of the deployment process, not as an afterthought. 

One-Click Monitor Creation from Incidents 

When you're in the middle of an incident investigation, switching contexts to set up monitoring for an unmonitored endpoint adds friction at exactly the wrong moment. Now you don't have to. A single click from the incident form is all it takes to create a synthetic monitor and ensure that endpoint is covered going forward. 

The feature works by using CMDB relationship data to automatically identify endpoints related to the affected service that aren't currently being monitored. Those endpoints are surfaced directly on the incident form — no separate audit or planning session required. When you create a monitor, it's automatically configured based on the endpoint type and service context, so there's no manual setup involved. 

Your monitoring coverage grows organically as your team responds to incidents. Gaps that would otherwise persist until the next planning cycle get closed in the moment they're discovered, turning a reactive process into a compounding investment in reliability. 

As your environment grows, so does the number of endpoints you’re responsible for, including APIs, services, third-party integrations, and edge workloads. The challenge is that visibility does not scale at the same pace. In fact, the more distributed your systems become, the harder it is to clearly see how those endpoints are performing in real time. 

That is where an incident-driven approach to monitoring becomes especially effective. 

Instead of trying to proactively instrument every endpoint, which quickly becomes expensive and outdated, you let real incidents highlight where your visibility gaps are. Each time something breaks or degrades, it reveals exactly which endpoint or signal you were not adequately tracking. 

By making it standard practice to add or improve monitoring as part of incident response, your coverage grows naturally over time. The endpoints that matter most, the ones that impact users, are the ones that quickly gain the deepest visibility. 

The result is a monitoring strategy that keeps pace with system complexity without adding significant overhead. You are not chasing complete coverage upfront. Instead, you are building it continuously, guided by real-world impact. 

How it works: ServiceNow analyzes the incident and surfaces related unmonitored endpoints using CMDB data. One click from the incident form creates a monitor, automatically configured for the endpoint type and service context. Coverage expands with each incident your team resolves. 

Getting Started 

API documentation: The complete API reference is available on the ServiceNow Documentation and Support site. 

One-click monitor creation: Ensure you have the most recent release of the Recommendation Framework plugin installed to activate incident-based monitor creation. 

Synthetic monitoring updates are available now in the ServiceNow store - for installation instructions and to learn more about implementing synthetic monitoring in your environment, visit the ServiceNow store or contact your ServiceNow representative. Have a unique use case that you want to share with our Product team? Feel free to reach out.