Synthetic monitoring

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Synthetic monitoring (also known as active monitoring or proactive monitoring) is website monitoring that is done using a Web browser emulation or scripted recordings of Web transactions. Behavioral scripts (or paths) are created to simulate an action or path that a customer or end-user would take on a site. Those paths are then continuously monitored at specified intervals for performance, such as: functionality, availability, and response time measures.

Synthetic monitoring is valuable because it enables a webmaster or an IT/Operations professional to identify problems and determine if a website or Web application is slow or experiencing downtime before that problem affects actual end-users or customers. This type of monitoring does not require actual Web traffic so it enables companies to test Web applications 24x7, or test new applications prior to a live customer-facing launch. This is a good complement when used with passive monitoring to help provide visibility on application health during off peak hours when transaction volume is low.[1]

When combined with traditional APM tools, synthetic monitoring can provide deeper visibility into end-to-end performance, regardless of where applications are running.[2]

Because synthetic monitoring is a simulation of typical user behavior or navigation through a website, it is often best used to monitor commonly trafficked paths and critical business processes. Synthetic tests must be scripted in advance, so it is not feasible to measure performance for every permutation of a navigational path an end-user might take. This is more suited for passive monitoring.

Synthetic testing is useful for measuring uptime, availability and response time of critical pages and transaction (how a site performs from all geographies) but doesn't monitor or capture actual end-user interactions, see Website monitoring. This is also known as Active monitoring that consists of synthetic probes and Web robots to help report on system availability and predefined business transactions.[3]

See also[edit]

References[edit]

  1. ^ "Prioritizing Gartner's APM Model". APM Digest. 15 March 2012. 
  2. ^ "Are You Monitoring Your SaaS Applications? If Not, You Should Be". APMdigest - Application Performance Management. 2017-02-14. Retrieved 2017-04-13. 
  3. ^ "The Anatomy of APM - 4 Foundational Elements to a Successful Strategy". APM Digest. 4 April 2012.