With this new feature, you will be able to find backend issues related to or even causing your synthetic monitor failures. While Synthetics monitors effectively detect website and API performance and availability issues, pinpointing backend issues that caused or are related to a failed monitor can be challenging. Leveraging Sematext’s all-in-one-platform capabilities enables you to efficiently identify the root cause of backend issues that led to the failure of your Synthetic monitor.
The New Troubleshoot Tab
When a Synthetics monitor run fails, you’ll now find a Troubleshoot tab in the failed runs flyout. This tab has options to drill into backend issues by correlating failed runs with metrics and logs.
Under this new Troubleshoot tab, you’ll find options to drill into related backend metrics or logs. Additionally, you will see a Trace Request option, which lets you troubleshoot by examining logs that backend applications and services emitted during the transaction started by the synthetic monitor’s request to the monitored endpoint.
Correlating with Metrics
Analyzing metrics related to incoming requests, such as request rate, response time, and error rate, can provide valuable insights into potential root causes. Sudden spikes in error rate or significant increases in response time around the time of monitor failure could indicate underlying issues.
Correlating with Logs
Alongside metrics analysis, reviewing error messages or warnings in logs associated with the monitored endpoint at the time of failure can provide valuable insights. Logs often reveal issues like misconfigurations, server resource limitations, or connectivity problems. By examining logs around the time of endpoint failure and zooming in on warnings and errors you can often figure out what issues related to applications and services encountered that caused the endpoint monitor to fail.
For more information, please refer to Troubleshoot Endpoint Issues docs.