This topic describes how to monitor the availability of local service processes and send alarm notifications if response timeouts occur or status codes indicate errors.
- The CloudMonitor agent must be installed before you can use the availability monitoring function. Check that you have installed the CloudMonitor agent on your specified instances before using this function.
- Monitoring tasks are performed once a minute.
- Before using the availability monitoring function, you must create an application group. For more information, see Create application groups.
- Log on to the CloudMonitor console.
- In the left-side navigation pane, click Application Groups.
- Find the target application group, and click the group name.
- In the left-side navigation pane, click Availability Monitoring.
- Click Create Configuration in the upper-right corner to go to the Create Availability Monitoring page.
- Target Server: the machine that initiates the detection. The detection source and target for local service availability monitoring are the same machine.
- Detection Type: Select URL or IP address.
- Detection Target: If you select HTTP(S), the syntax is localhost:port/path. If you select TELNET, the syntax is 127.0.0.1:port. Both are useful for different applications. If you want to detect whether Tomcat is responding properly, select HTTP(S) and enter localhost:8080/monitor. If you want to detect the connectivity of MySQL, select TELNET and enter 127.0.0.1:3306.
Both Status Code and Response Time are used as the metrics of availability monitoring. An alarm is triggered when either metric value reaches the specified threshold. An alarm notification is sent to the alarm contact group of the corresponding application group. For local availability monitoring, set the status code greater than 400.
- Status Code: An alarm is triggered when the returned status code meets the alarm rule.
- Notification Method: the method by which alarm notifications are sent.
- Advanced Configuration:
- Muted For: a period in which your alarm rules are muted so that alarm notifications will be silenced even if conditions specified in your alarm rules are met.
- Effective From: a period in which an alarm rule is effective with alarms possibly triggered in the case that the conditions specified in your alarm rules are met.
- Click OK to save your settings. When your service does not respond, an alarm notification is sent with the method you specified, such as SMS messages and emails.
- To view the details of unhealthy hosts, click the number of Unhealthy Hosts in the availability monitoring task list.