Blog Post

Active vs Passive Monitoring

The widespread move to Cloud computing and use of SaaS tools stimulated the need for synthetic monitoring that emulates end-user transactions using behavioral scripts.

External web performance monitoring tools utilize agents to simulate user activity on a given URL. These tools are also known as Active Monitoring Tools (as they actively simulate transactions) or Synthetic Monitoring Tools. Synthetic Monitoring Solutions rely on browser emulators or actual automated browsers to execute HTTP activity, in others words, to request URLs or load webpages. In both cases the synthetic agent sees the transaction from the perspective of the client (requester) and often does not have the perspective of the server/application. On the other side Real User Monitoring devices, also known as Passive Monitoring Tools, get the perspective from your datacenter by gathering TCP packets at the switch/router inside the web-site datacenter.  They monitor any activity to your servers and applications, and can gather Real User Performance data in regards to your application or content.

There are several key differences between the two:

  • Synthetic Monitoring traditionally occurs from outside the datacenter, and is affected by the network differently than Passive Monitoring. (Keep in mind that packets from the client to the server can take a different path from the packets coming from the server to the client).
  • Passive Monitoring looks at the traffic generated by real users of the websites and robots. Synthetic Monitoring looks only at the activity they generate based on your instructions. The network of a real user is different from that of the synthetic monitors (who are usually on datacenters) hence the results can be quite different.
  • The biggest limitation of Passive Monitoring is that the data collected is limited to the traffic on the network the router is attached to, and it does not collect data for other requests like CDNs, Advertising, etc. Synthetic monitors on the other side request and monitor everything on the page.

When we started Catchpoint, we looked at both monitoring methods and decided to go with synthetic monitoring. The main reason for this was that we foresaw the widespread move to Cloud computing and use of SaaS tools, and that implementing Passive devices would be limited by this distribution of services. With Synthetic Monitoring you can monitor a webpage and anything referenced by it, including CDN, adservers, and any widgets. To mitigate the loss of actual end-user performance data, we then built Catchpoint Glimpse, which relies on JavaScript to collect Real User performance data from the user perspective. We brought the ability to overlay the data from the two monitors in one screen to correlate the Synthetic monitoring data from the backbone with that of the real users on the page, to understand the full performance impact in the end-user.


Synthetic Monitoring
Real User Monitoring
Network Reachability
Workforce Experience
SaaS Application Monitoring
This is some text inside of a div block.

You might also like

Blog post

Traceroute InSession: A traceroute tool for modern networks

Blog post

The cost of inaction: A CIO’s primer on why investing in Internet Performance Monitoring can’t wait

Blog post

DNS Security: Fortifying the Core of Internet Infrastructure