All Products
Search
Document Center

Server Load Balancer:Integrate CLB with Managed Service for Prometheus

Last Updated:Sep 30, 2026

You can use Managed Service for Prometheus to view monitoring data for Classic Load Balancer (CLB) through metrics, dashboards, and alerts. This topic describes how to integrate CLB with Managed Service for Prometheus.

Overview

Managed Service for Prometheus is compatible with the open source Prometheus ecosystem, supports monitoring for a variety of components, provides multiple out-of-the-box dashboards, and offers a fully managed Prometheus service. For more information, see What is Managed Service for Prometheus?.

CLB integrates with Managed Service for Prometheus through Hybrid Cloud Monitoring, which is a paid service. The following table provides details.

Integration type

Description

Metric fees

Storage fees

Hybrid Cloud Monitoring (paid)

Managed Service for Prometheus pulls metrics by calling the CloudMonitor API. After you integrate CLB, you can use cloud service dashboards and alert rules to monitor your CLB instances and receive alerts.

CloudMonitor charges data transfer fees for CLB metric reporting.

For pricing details, see Export Real-Time Data.

Managed Service for Prometheus stores reported metrics for free.

Prerequisites

Create a Prometheus instance

  1. Log on to the Cloud Monitor console.

  2. In the top navigation bar, select a region, and then click Create Prometheus Instance.

  3. On the Create Instance page, configure the following parameters and click Create Now.

    Parameter

    Description

    Instance type

    Select General-purpose Instance or Global Aggregation Instance. This topic uses a General-purpose Instance as an example.

    Note
    • General-purpose Instance: A general-purpose Prometheus instance that fits most use cases. You can use it as remote storage (Remote Write) for a self-managed Prometheus cluster, or to ingest metrics from containers, cloud services, hosts, and more.

    • Global Aggregation Instance: A virtual aggregation instance for multiple Alibaba Cloud Prometheus instances. It provides unified metric queries, a unified Grafana data source, and unified alerting.

    Storage duration

    You can select a storage duration of 15 Days, 30 Days, 60 Days, 90 Days, or 180 Days.

Integrate CLB with Managed Service for Prometheus

  1. Log on to the ARMS console.

  2. In the navigation pane on the left, click Integration Center.

  3. On the Integration Center page, click the Middleware tab, and then click Alibaba Cloud SLB.

  4. In the Alibaba Cloud SLB panel, select the data storage region and click OK. The integration takes about 1 to 2 minutes to complete.

  • Metrics

    On the Collect Metrics tab, you can view the monitoring metrics for CLB.

    CLB metrics available in Managed Service for Prometheus

    Metric

    Description

    AliyunSlb_ActiveConnection

    Active TCP connections per second

    AliyunSlb_DropConnection

    Connections dropped by listeners per second

    AliyunSlb_DropPacketRX

    Inbound packets dropped by listeners per second

    AliyunSlb_DropPacketTX

    Outbound packets dropped by listeners per second

    AliyunSlb_DropTrafficRX

    Inbound bits dropped by listeners per second

    AliyunSlb_DropTrafficTX

    Outbound bits dropped by listeners per second

    AliyunSlb_GroupActiveConnection

    Active TCP connections per second, by server group

    AliyunSlb_GroupNewConnection

    New TCP connections, by server group

    AliyunSlb_GroupTotalTrafficRX

    Total inbound bandwidth, by server group

    AliyunSlb_GroupTotalTrafficTX

    Total outbound bandwidth, by server group

    AliyunSlb_GroupTrafficRX

    Inbound bandwidth, by server group

    AliyunSlb_GroupTrafficTX

    Outbound bandwidth, by server group

    AliyunSlb_GroupUnhealthyServerCount

    Number of unhealthy backend ECS instances, by server group

    AliyunSlb_HealthyServerCountWithRule

    Number of healthy backend ECS instances for Layer 7 forwarding rules

    AliyunSlb_HealthyServerCount

    Number of healthy backend ECS instances that pass health checks

    AliyunSlb_InactiveConnection

    Inactive TCP connections

    AliyunSlb_InstanceActiveConnection

    Active connections to the instance per second

    AliyunSlb_InstanceDropConnection

    Connections dropped by the instance per second

    AliyunSlb_InstanceDropPacketRX

    Inbound packets dropped by the instance per second

    AliyunSlb_InstanceDropPacketTX

    Outbound packets dropped by the instance per second

    AliyunSlb_InstanceDropTrafficRX

    Inbound bits dropped by the instance per second

    AliyunSlb_InstanceDropTrafficTX

    Outbound bits dropped by the instance per second

    AliyunSlb_InstanceInactiveConnection

    Inactive connections to the instance per second

    AliyunSlb_InstanceMaxConnection

    Maximum concurrent connections to the instance per second

    AliyunSlb_InstanceMaxConnectionUtilization

    Maximum connection utilization of the instance

    AliyunSlb_InstanceNewConnection

    New connections to the instance per second

    AliyunSlb_InstanceNewConnectionUtilization

    New connection utilization of the instance

    AliyunSlb_InstancePacketRX

    Inbound packets to the instance per second

    AliyunSlb_InstancePacketTX

    Outbound packets from the instance per second

    AliyunSlb_InstanceQps

    Layer 7 QPS of the instance

    AliyunSlb_InstanceQpsUtilization

    Layer 7 QPS utilization of the instance

    AliyunSlb_InstanceRt

    Layer 7 RT of the instance

    AliyunSlb_InstanceStatusCode2xx

    Number of Layer 7 2xx status codes on the instance per second

    AliyunSlb_InstanceStatusCode3xx

    Number of Layer 7 3xx status codes on the instance per second

    AliyunSlb_InstanceStatusCode4xx

    Number of Layer 7 4xx status codes on the instance per second

    AliyunSlb_InstanceStatusCode5xx

    Number of Layer 7 5xx status codes on the instance per second

    AliyunSlb_InstanceStatusCodeOther

    Number of Layer 7 other status codes on the instance per second

    AliyunSlb_InstanceTrafficRX

    Inbound bits to the instance per second

    AliyunSlb_InstanceTrafficTX

    Outbound bits from the instance per second

    AliyunSlb_InstanceTrafficTXUtilization

    Outbound bandwidth utilization of the instance

    AliyunSlb_InstanceUpstreamCode4xx

    Number of Layer 7 upstream 4xx codes on the instance per second

    AliyunSlb_InstanceUpstreamCode5xx

    Number of Layer 7 upstream 5xx codes on the instance per second

    AliyunSlb_InstanceUpstreamRt

    Layer 7 upstream RT of the instance

    AliyunSlb_MaxConnection

    Concurrent connections on ports

    AliyunSlb_NewConnection

    New TCP connections

    AliyunSlb_PacketRX

    Inbound packets per second

    AliyunSlb_PacketTX

    Outbound packets per second

    AliyunSlb_Qps

    Layer 7 QPS of listeners

    AliyunSlb_Rt

    Layer 7 RT of listeners

    AliyunSlb_StatusCode2xx

    Number of Layer 7 2xx status codes of listeners per second

    AliyunSlb_StatusCode3xx

    Number of Layer 7 3xx status codes of listeners per second

    AliyunSlb_StatusCode4xx

    Number of Layer 7 4xx status codes of listeners per second

    AliyunSlb_StatusCode5xx

    Number of Layer 7 5xx status codes of listeners per second

    AliyunSlb_StatusCodeOther

    Number of Layer 7 other status codes of listeners per second

    AliyunSlb_TrafficRXNew

    Inbound bandwidth

    AliyunSlb_TrafficTXNew

    Outbound bandwidth

    AliyunSlb_UnhealthyServerCount

    Number of unhealthy backend ECS instances

    AliyunSlb_UnhealthyServerCountWithRule

    Number of unhealthy backend ECS instances for Layer 7 forwarding rules

    AliyunSlb_UpstreamCode4xx

    Number of Layer 7 upstream 4xx codes of listeners per second

    AliyunSlb_UpstreamCode5xx

    Number of Layer 7 upstream 5xx codes of listeners per second

    AliyunSlb_UpstreamRt

    Layer 7 upstream RT of listeners

  • Alerts

    On the Alert Rule Template tab, you can create Prometheus alert rules and view alert information. For details on how to create an alert rule, see Create a Prometheus alert rule.

  • Dashboards

    On the Start Integration tab, click Integration Management, choose Component Management > Dashboards, and then click SLB to view the performance metrics of a specific CLB instance.

Integrate a self-managed Prometheus server

You can configure your self-managed Prometheus server to send data to Managed Service for Prometheus using the remote write feature. For details, see Prometheus instance for general-purpose scenarios.

Disable CLB monitoring

  1. Log on to the Cloud Monitor console.

  2. On the Instances page, select the target region in the top navigation bar. In the row for the target instance, click Delete in the Actions column.

  3. In the dialog box that appears, click OK.

Related topics