Monitoring Configuration Best Practices

Product Team
Updated 10 months ago

What You'll Learn on This Page

This page outlines best practices for configuring and maintaining monitors within your RADAR environment. It provides guidance on selecting the most appropriate monitoring methods for each service type, validating and tracking monitor responsiveness, and ensuring accurate performance visibility. Following these practices helps maintain reliable monitoring data, supports timely issue detection, and ensures ongoing validation of your DDoS protection posture.


  1. Select the Most Service-Specific Monito

    When configuring monitors for Targets, select the monitor type that best reflects the behavior of the service being tested. Using service-specific monitors ensures that performance and availability are measured accurately under realistic conditions.
    For example, select HTTPS GET (with JS) for web servers that expect browser-based traffic to validate end-to-end responsiveness and content delivery. Aligning the monitor type with the service characteristics provides more reliable visibility into actual user experience and protection effectiveness


  2. Validate Monitor Responsiveness After Configuration

    After adding a new monitor, validate that it responds within an acceptable timeframe to ensure correct configuration and connectivity. Consistent and timely responses confirm that the monitor is functioning properly and accurately representing the Target’s availability. 

    If response times are unusually high or inconsistent, contact the MazeBolt Technical Team to help identify potential configuration or connectivity issues. Reliable monitor responsiveness is essential for maintaining accurate visibility across your protected environment.

Was this article helpful?