Synthetic monitoring

This article has multiple issues. Please help or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article or section contains close paraphrasing of one or more non-free copyrighted sources. Relevant discussion may be found on the talk page. Ideas in this article should be expressed in an original manner. (August 2016) (Learn how and when to remove this template message) This article is written like a personal reflection, personal essay, or argumentative essay that states a Wikipedia editor's personal feelings or presents an original argument about a topic. Please by rewriting it in an encyclopedic style. (July 2017) (Learn how and when to remove this template message) This article may be too technical for most readers to understand. Please to make it understandable to non-experts, without removing the technical details. (October 2021) (Learn how and when to remove this template message) (Learn how and when to remove this template message)

In software design, web design, and electronic product design, synthetic monitoring (also known as active monitoring or proactive monitoring) is a monitoring technique that is done by using an simulation or scripted recordings of transactions. Behavioral scripts (or paths) are created to simulate an action or path that a customer or end-user would take on a site, application or other software (or even hardware). Those paths are then continuously monitored at specified intervals for performance, such as: functionality, availability, and response time measures.

Synthetic monitoring enables a webmaster or an IT/Operations professional to identify problems and determine if a website or application is slow or experiencing downtime before that problem affects actual end-users or customers. This type of monitoring does not require actual traffic, thus the name synthetic, so it enables companies to test applications 24x7, or test new applications prior to a live customer-facing launch. This is usually 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]

Synthetic monitoring will report myriad metrics, and it's up to the a webmaster or an IT/Operations professional to identify which ones are most important. Common metrics from synthetic website monitoring includes Time to First Byte, Speed Index, Time to Interactive, and Page Complete.^[4]

See also[]

• Application performance management
• Website monitoring

References[]