Help Center/ Cloud Eye/ Best Practices/ Scenario-specific Cases/ Service Monitoring on E-Commerce Platforms/ Server Monitoring
Updated on 2025-12-23 GMT+08:00
View PDF
Share

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 server monitoring that is system-wide, active, and fine-grained 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

  1. Log in to the management console.
  2. In the upper left corner, select a region and a project.
  3. Choose Service List > Cloud Eye.
  4. In the navigation pane, choose Server Monitoring.
  5. Locate the target ECS. In the Operation column, click More and select Create Alarm Rule.
  6. 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 in the same alarm rule

    The value cannot be changed.

    Monitoring Scope

    Specific resources

    Monitoring scope the alarm rule applies to.

    Method

    Configure manually

    Select a rule triggering method.

    Metric Name

    ECSs - Process - ProcessIDs / (Agent)Process CPU Usage

    Select a metric for triggering alarms.

    Alarm Policy

    If the metric value is greater than or equal to 80% for three consecutive times, an alarm is generated once every day.
    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.
  7. Configure alarm notification parameters.
    Table 2 Parameters for configuring alarm notifications

    Parameter

    Example Value

    Description

    Alarm Notifications

    Enabled

    Whether to send an alarm notification when an alarm is triggered.

    Notified By

    Topic subscriptions

    Select an alarm notification mode.

    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 Notified By is set to Topic subscriptions, you need to set the notification window.
    • Cloud Eye sends notifications only within the specified time period.

    Trigger Condition

    Generated alarm, Cleared alarm

    This parameter is available when Notified By is set to Topic subscriptions or Notification groups. You can select Generated alarm, Cleared alarm, or both.

After the alarm rule is created, once the service volume soars and the specified threshold is reached, Cloud Eye immediately informs you of the resource exception.