Server Monitoring
ECSs are the cores of an e-commerce platform. Slight changes in ECS performance may cause dramatic fluctuation of e-commerce services or even service interruptions, resulting in huge losses.
Server Monitoring provides Basic Monitoring and OS Monitoring of different monitoring granularities. Basic Monitoring monitors metrics reported by ECSs. OS Monitoring provides system-wide, active, and fine-grained server monitoring after the Agent is installed on an ECS.
This section takes (Agent) CPU Usage as an example to describe how to use server monitoring. To reserve some processing performance for proper server running, you are advised to set its threshold to 80% and let Cloud Eye generate an alarm when the usage exceeds the threshold for three consecutive times.
Scenarios
In e-commerce scenarios such as promotions, flash sales, and red-hot sellers, the number of instantaneous visits multiplies to tens to hundreds of times than that in days without activities, which results in heavy server load and slow system response.
You can configure alarm rules for ECS metrics, for example, CPU usage. When the CPU usage reaches the threshold, an alarm notification is sent to remind you to handle the exception promptly.
Prerequisites
The Agent has been installed. For details, see Agent Installation and Configuration.
Procedure
- Log in to the Cloud Eye console.
- In the navigation pane, choose Server Monitoring.
- Locate the target ECS. In the Operation column, click More and select Create Alarm Rule.
- On the Create Alarm Rule page, set the alarm parameters as prompted. Alarm Type, Cloud Product, Resource Level, Monitoring Scope, and Instance are preset by default.
Table 1 Parameters for configuring an alarm rule for an ECS Parameter
Example Value
Description
Alarm Type
Metric
Alarm type that the alarm rule applies to. The value cannot be changed.
Cloud Product
Elastic Cloud Server - ECSs
Name of the service for which the alarm rule is configured. The value cannot be changed.
Resource Level
Cloud product
A cloud product has many specific dimensions. If you set Resource Level to Cloud product, metrics across dimensions can be configured in the same alarm rule. If you set it to Specific dimension, only metrics of the specified dimension can be configured for the same alarm rule
The value cannot be changed.
Monitoring Scope
Specific resources
Monitoring scope the alarm rule applies to.
Method
Configure manually
Method for configuring an alarm policy. You can select a template or customize an alarm policy.
Alarm Policy
If Raw data of Process - ProcessIDs / (Agent)Process CPU Usage >= 80% for 3 times (consecutively), an alarm is triggered Daily.
Policy for triggering an alarm.NOTE:If the alarm is not cleared after it is generated, an alarm is reported every day.
Alarm Severity
Major
Severity of alarms.
- Configure alarm notification parameters.
Table 2 Alarm notification parameters Parameter
Example Value
Description
Alarm Notifications
Enabled
Whether to send an alarm notification when an alarm is triggered.
Notified By
Topic subscriptions
Select a notification method. You can select notification policies, contact groups, or topic subscriptions.
Recipient
Account contact
- If you select Topic subscriptions for Notified By, select one or more notification recipients.
- If Recipient is set to Account contact, notifications will be sent to the registered phone number and email address.
Notification Window
00:00–23:59
If you select Notification groups or Topic subscriptions for Notified By, you need to set the notification window. The system sends notifications only within the notification window.
Trigger Condition
Generated alarm and Cleared alarm
This parameter is available when Notified By is set to Notification groups or Topic subscriptions. You can select Generated alarm, Cleared alarm, or both.
Notification Template
System template
This parameter is only available if you set Notified By to Notification groups or Topic subscriptions. You can select an existing template or create one to send alarm notifications.
After the alarm rule is created, when the service volume surges and the metric data reaches the threshold, Cloud Eye notifies you of the cloud resource exception in real time.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot