Using Custom Monitoring
The Custom Monitoring page displays all custom metrics reported by users. You can use simple API requests to report collected monitoring data of those metrics to Cloud Eye for processing and display.
For details about how to add monitoring data, see Adding Monitoring Data.
Viewing Custom Monitoring
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Custom Monitoring.
- On the Custom Monitoring page, view the data reported by yourself through API requests, including custom services and metrics.
- Locate the row that contains the target cloud service resource and click View Metric in the Operation column.
On the page displayed, you can view graphs based on raw data collected in 1h, 3h, and 12h. In the upper right corner of each graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed.
- If you want to view metric details, hover your mouse over a graph and click in the upper right corner.
In the upper left corner, you can see six default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. To view historical monitoring data for any period during the last six months, customize the monitoring period by setting Select Range in the upper right corner.
In the upper left corner of the graph, click Settings to configure the rollup method.
Creating an Alarm Rule
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Custom Monitoring.
- Locate the target cloud service resource and click Create Alarm Rule in the Operation column.
- Configure the alarm rule name, alarm policy, and alarm notification as prompted.
After you create the alarm rule, if the custom metric data reaches the threshold, Cloud Eye immediately notifies you through SMN that an exception has occurred.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.