When does an instance go into trouble, critical, or down status?
When performance metrics of your instance exceeds the configured threshold values, your application / instance
either goes into Trouble or Critical status, based on your applied settings. When your application/ instance fails to communicate with the server, it is then marked as Down.
Related Articles
Configuring the status module (mod_status) for Apache monitoring
The Apache mod_status module enables users to view detailed performance metrics of the Apache web server. You must enable and configure the mod_status correctly in the Apache configuration file to get performance metrics from Apache and view ...
How to configure the NGINX status page for monitoring NGINX performance
The NGINX plugin uses the NGINX status page to pull the performance metrics of the NGINX server. You may encounter the following errors while installing the NGINX plugin integration: Error_code : HTTP Error 404: This error usually indicates that the ...
Meaning of the trouble message - "Content Length Modified"
This alert indicates that the content length of your monitored website has changed compared to the previous check. Even minor textual changes on your website will be reflected as a trouble alert. How it works Under Threshold Configuration, if you ...
What is Polling in Site24x7?
Site24x7 captures the uptime and critical performance status of your websites, servers, and web applications. To achieve this, Site24x7 persistently checks the availability and collects relevant performance data from your monitored resources at ...
How to enable or disable anomaly alerts
Understanding alerts In Site24x7, there are two different types of alerts in anomaly detection: Status change alert: Triggered when there is a change in the monitor status, such as Trouble, Critical, or Down. Anomaly alert: Triggered when irregular ...