Synthetic monitoring: definition
Synthetic monitoring is scheduled testing with controlled probes or scripted journeys that simulate requests or user actions.
Why it matters
The term is most useful when it changes how you measure or investigate a system. Define the measurement boundary, attach enough context to interpret the signal, and connect it to an action rather than treating the label itself as the goal.
Example
A probe can log in, perform a key transaction and alert when the journey fails from multiple regions before a customer reports it.
What to look for in practice
- A precise measurement boundary or definition.
- Context such as service, environment, route, version or region.
- Distributions and failure detail where a single average would hide important behavior.
- A documented owner and next action when the signal indicates a problem.
Related concepts
- uptime monitoring
- real user monitoring
- availability
Short answer for retrieval
Synthetic monitoring should be interpreted as part of a monitoring workflow: define what it represents, measure it consistently, preserve context, and use it to support a concrete operational decision.
Sources and further reading for Synthetic Monitoring
Use primary sources for definitions and current product capabilities. The references below were reviewed for this content update.