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 help improve it 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 help improve it to make it understandable to non-experts, without removing the technical details. (October 2021) (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 a 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.[1][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 transactions (how a site performs from all geographies) but doesn't monitor or capture actual end user interactions, see Website monitoring.[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]

Demand for synthetic monitoring has grown exponentially corresponding to the underlying growth in websites/applications. IT/Operations staff need mechanisms to identify health and performance issues in advance of their customers identifying and reporting them to avoid customer satisfaction issues. To accomplish this they can write custom simulation scripts, or leverage the growing number of commercial synthetic monitoring solutions. Example include:

By implementing Synthetic Monitoring IT/Operations staffs are able to identify application issues in advance of them becoming critical, and take remedial action. Identifying such issues can be difficult because of:

See also

References

  1. ^ "Prioritizing Gartner's APM Model". APM Digest. 15 March 2012. Archived from the original on 22 March 2012. Retrieved 28 April 2012.
  2. ^ "Are You Monitoring Your SaaS Applications? If Not, You Should Be". APMdigest - Application Performance Management. 2017-02-14. Archived from the original on 2017-04-14. Retrieved 2017-04-13.
  3. ^ "The Anatomy of APM - 4 Foundational Elements to a Successful Strategy". APM Digest. 4 April 2012. Archived from the original on 8 June 2012. Retrieved 18 May 2012.
  4. ^ "Site Speed Metrics Explained - TTFB, Speed Index, Interactive, Load, Complete, and more". MachMetrics Speed Blog. 2019-02-22. Archived from the original on 2020-03-18. Retrieved 2020-01-17.
Category