This topic describes how to configure local service availability monitoring so that you can receive alert notification if the service does not respond within a specified timeout period or when an error status code is returned.
Local service availability monitoring sends alert notification to identify situations where local services are unresponsive or when an error status code is returned.
- Local service availability monitoring depends on the CloudMonitor agent. Ensure that the CloudMonitor agent has been installed on the monitored host. For more information, see Introduction to the CloudMonitor GoLang agent.
- Before you use local service availability monitoring, you must Create application groups.
- Local service availability monitoring depends on the CloudMonitor agent to run properly. Ensure that the CloudMonitor agent has been installed on the monitored host.
- An availability test is performed once a minute.
- Log on to the CloudMonitor console.
- In the left-side navigation pane, click Application Groups. The Application Groups page is displayed.
- Click the name of the application group for which you want to create a local service availability monitoring task. The application group details page is displayed.
- In the left-side navigation pane, click Availability Monitoring. The Availability Monitoring page is displayed.
- Click Create Configuration in the upper-right corner. The Create Availability Monitoring page is displayed.
- Set Task Name and Target Server. You can configure the same detection rule to be applied to all hosts in the group or just a portion of hosts in the group.
- Set Detection Type to URL or IP Address, ApsaraDB for RDS, or ApsaraDB RDS for Redis. Set Detection Target.
- In the Alert Configuration section, set Status Code and Response Time. An alert is triggered if the conditions of either parameter are met. Alerts are sent to the contact group of the corresponding application group.
- Click OK. If your service does not respond within the timeout period, you will receive alert notification through text messages, emails, or other channels.
- (Optional) The availability monitoring list displays the number of unhealthy hosts. Click Unhealthy Hosts to view the details of the abnormal hosts.
- Monitoring Configuration section:
- Target Server: the host that initiates the test. Target Server and Detection Target are the same host.
- Detection Type: Select URL or IP Address.
- Detection Target: If you select HTTP(S), enter the target address in the format of
localhost:port/path. If you select TELNET, enter the target address in the format of
127.0.0.1:port. For example, to test whether Tomcat responds normally, select HTTP(S) and enter
localhost:8080/monitor. To test the connectivity of MySQL, select TELNET and enter
- Alarm Configuration section:
Both Status Code and Response Time are used as the metrics of availability monitoring. An alert is triggered if either metric value reaches the specified threshold. Alerts are sent to the contact group of the corresponding application group. For local availability monitoring, set the status code greater than 400.
- Status Code: An alert is triggered if the returned status code meets the conditions set in the alert rule.
- Notification Method: the method by which alerts are sent.
- Advanced Configuration:
- Muted For: a period when your alert rules are muted so that no alerts are sent even if the conditions specified in your alert rules are met.
- Effective From: a period when the alert rules are effective. Alerts are sent if the conditions specified in your alert rules are met during this period. You can configure these parameters based on your actual needs.