This alert monitors the occurrence of errors during synthetic monitoring of a specified URL. Synthetic monitoring errors indicate potential issues with the availability or performance of the URL, which could impact user experience or application functionality. The alert is triggered when the synthetic monitoring service detects one or more errors, such as HTTP response codes above 400 or timeouts, during a predefined monitoring period. Monitoring this metric helps ensure that critical URLs are accessible and functioning correctly, allowing for quick identification and resolution of issues before they affect users. Customization Guidance: Threshold: Adjust the threshold based on the acceptable error rate for your specific URL or application. Monitoring Period: Set the monitoring period to align with the typical access frequency or expected activity patterns for the URL. Notification Frequency: Balance notification frequency to avoid alert fatigue while ensuring prompt awareness of critical issues. Action: If this alert is triggered, consider investigating the URL for potential issues, such as server downtime, configuration errors, or connectivity problems. Implement fixes or escalate to the appropriate team to restore normal operation.

This alert monitors the average duration of synthetic URL tests, detecting when it exceeds a specified threshold, which may indicate potential performance degradation or bottlenecks in the monitored application or service. The alert is triggered when the average synthetic URL duration surpasses 40 over a 10-minute period. Monitoring this metric helps ensure the monitored application's performance and responsiveness, enabling proactive identification and resolution of latency issues. Customization Guidance: Threshold: Adjust the threshold based on acceptable performance benchmarks for your application and user experience standards. Monitoring Period: Modify the monitoring period to reflect the frequency of synthetic test execution and typical performance trends. Notification Frequency: Set notification frequency to avoid redundant alerts while ensuring timely responses to critical issues. Action: If this alert is triggered, consider investigating the specific synthetic URL for delays, checking for backend or network issues, and optimizing any identified bottlenecks to restore performance.