This guide has been created by Catchpoint to answer common questions from practitioners about synthetic monitoring. The articles are organized by topic, and they can be read either separately or together as a whole set.
You will learn about:
- The differences between synthetic monitoring and real user monitoring
- The benefits of synthetic monitoring for improving end-user experience
- Troubleshooting tips for interpreting synthetic monitoring results
- What features to look for in a synthetic monitoring tool
What is Synthetic Monitoring?
Synthetic Monitoring emulates end-user transactions using behavioral scripts to validate and measure workflow performance from multiple test points. This kind of monitoring is well-suited for resolving issues because it detects slowness or downtime before your end-users notice any impact.
Why use Synthetic Monitoring?
Synthetic monitoring enables you to establish performance baselines for your digital services or applications. By emulating multi-protocol synthetic transactions at configurable intervals, you can establish daily, weekly, monthly baselines for any important set of performance measures (e.g., user experience, network, DNS, CDN, or API performance). Continuous synthetic monitoring then leverages these established baselines to detect any deviations and alert you of the root cause.
Additional uses include:
- Conducting performance analysis while your services are being tested in a staging environment prior to production release
- Conducting availability and performance analysis during non-peak hours (low or no traffic)
- Conducting competitive analysis of responsiveness to benchmark against other applications or websites
How Synthetic Monitoring Improves Service Quality
Product success requires consistency—in content, in availability, in performance—regardless of the target market or service niche. Users have high expectations for application responsiveness and will quickly switch to alternative solutions. Synthetic monitoring helps you manage the perception of your applications across every major dimension of user interactivity.
Much like Maslow’s Hierarchy of Needs for human wellness, your service’s wellness also has its own hierarchy of needs. Specific to synthetic monitoring, we have defined the following four levels:
- Availability - monitor availability
- Performance - measure performance
- Reachability - extend reachability
- Reliability - trend reliability
At a foundational level, your service must be up and running. Once it’s available, users expect it to be fast. Next, you must enable your users to access the service from anywhere in the world or at least make it accessible from all regions within your target market. And finally, your website must be consistent in how it’s available, performing, and reachable.
"Product success requires consistency—in content, in availability, in performance—regardless of the target market or service niche. Users have high expectations for application responsiveness and will quickly switch to alternative solutions. Synthetic monitoring helps you manage the perception of your applications across every major dimension of user interactivity."
We have defined this as reliability; however, it is sometimes known as a Service Level Agreement (SLA) which is measured as a percentage of time (such as 99.999%). Fortunately, synthetic monitoring is well suited to test all of the aspects of service quality as defined.
Where Synthetic Monitoring Happens
Your users are on a quest to achieve a task, discover new information, or experience entertainment. Although seemingly instant, their success requires getting past several checkpoints across the internet. For example, they must:
- Use an endpoint device with adequate hardware and software.
- Access an active internet connection with sufficient bandwidth.
- Resolve your domain name into an IP address to send traffic to it.
- Load any cached content from a Content Distribution Network (CDN) node close to their geographic location.
- Get routing directions for their data packets from a Border Gateway Protocol (BGP) as they relay across Internet Service Providers (ISP).
- Connect to the cloud service provider that is hosting your application service.
- And perhaps wait for your application to get additional data from a third-party API before responding.
This journey happens with every user interaction that requires content from your service. Synthetic Monitoring allows your team to segment each of these checkpoints across your user’s journey to quickly triangulate problems blocking their path to your application from their local region.
Why Synthetic Monitoring is So Effective
Synthetic monitoring validates your application’s health at all hours of the day, in all relevant locations, across every network provider, and for every major or minor transaction. It does not require active users to measure performance. Information gathered by synthetic monitoring is segmented by network checkpoints found along the data path. Without synthetic monitoring, valuable network information is nebulous and often the cause of performance blind spots.