Help Center/Cloud Eye/Best Practices/Scenario-specific Cases/Live Streaming Monitoring/ELB Monitoring
Updated on 2025-12-23 GMT+08:00
View PDF
Share

ELB Monitoring

In live video streaming, sudden increase of network access traffic may cause service instability. Therefore, most live video streaming platforms use ELB to automatically distribute traffic to multiple ECSs.

Stable and reliable load balancing is critical to the proper running of live video streaming. Cloud Eye can monitor unhealthy backend servers and concurrent connections of load balancers to ensure proper running of your services.

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, click My Dashboards > Custom Dashboards.
  5. Locate the dashboard for which you want to add a graph and click its name.
  6. In the upper part of the page, click Create and then Create Graph.
    In the Add Graph dialog box, add the concurrent connections of all enhanced elastic load balancers involved in live video streaming to the same graph.
    Figure 1 Adding a graph

    The running trends of all concurrent connections in the same live video streaming must be consistent. If the trend of one or more concurrent connections is inconsistent with other trends, an exception occurs. In this case, locate the cause and rectify the fault immediately.

  7. In the navigation pane, choose Alarm Management > Alarm Rules.
  8. Click Create Alarm Rule in the upper right corner the page.
  9. On the displayed page, set the parameters as prompted. For details about alarm rule parameters, see Creating an Alarm Rule and Notifications.
    Figure 2 Creating an alarm rule
    Table 1 Alarm content parameters

    Parameter

    Example Value

    Description

    Alarm Type

    Metric

    Alarm type that the alarm rule applies to.

    Cloud Product

    Elastic Load Balance - Elastic Load Balancers

    Name of the monitored service.

    Resource Level

    Cloud product

    A cloud product has many specific dimensions. If you set this parameter 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.

    Monitoring Scope

    All resources

    Monitoring scope the alarm rule applies to.

    Method

    Configure manually

    Method of triggering the rule.

    Metric Name

    Elastic Load Balances > Unhealthy Servers

    Metric for triggering alarms.

    Alarm Policy

    If Raw data of the metric >=1 for 1 time, a Critical alarm is triggered Daily.

    Policy for triggering an alarm.

    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

    Alarm notification mode.

    Recipient

    Account contact

    • If Notified By is set to Topic subscriptions, you need to select the recipients.
    • If Recipient is set to Account contact, notifications will be sent to the registered mobile 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 and Cleared alarm

    If you set Alarm Type to Notification groups or Topic subscriptions, select Generated alarm, Cleared alarm, or both for this parameter.

  10. Click Create.

    When ELB is abnormal, Cloud Eye interworks with SMN to notify you of the resource exception in real time.