DocsICP FilingConsole
官方文档
首页

CloudLens for CLB (formerly SLB Log Center)

更新时间：
复制 MD 格式
产品详情
我的收藏

CloudLens for CLB analyzes Classic Load Balancer (CLB) access logs, configuration audit logs, and CloudMonitor events. CloudLens for CLB also provides metric analysis in seconds, real-time alerting, and AIOps-based health checks. Use CloudLens for CLB to monitor client behavior, geographic distribution, request success rates, and response latency.

Product trial

The CloudLens for CLB demo in the SLS Playground includes built-in CLB instances, demo data, and charts for you to explore the features.

Click CloudLens for CLB to try it out.

Important

SLS Playground data is for demonstration only. Do not use it in production.

Features

CloudLens for CLB aggregates real-time access logs and provides intelligent health checks and real-time alerting.

image

  • Centrally manage all CLB instances in your Alibaba Cloud account.Feature overview

  • Enable data ingestion for instance logs (access logs) and global logs (configuration audit logs and CloudMonitor events) in one click. Manage ingestion status centrally. Enable data ingestion.

    • Access logs record request time, client IP address, latency, request path, and server response for all requests sent to a load balancer.

    • Configuration audit logs include CLB configuration change logs and resource non-compliance logs.

    • CloudMonitor events track SLB certificate expiration.

    Feature overview

  • Store, query, and analyze CLB access logs in real time.Feature overview

  • View visualization reports for monitoring and instance health checks. Subscribe to reports by email or DingTalk.Feature overview

  • Configure custom alerts delivered through Message Center, text message, email, voice call, DingTalk, or custom webhooks.Feature overview

  • Extract real-time metrics from raw access logs, including PVs, request success rate, average latency, P50/P99 latency, and inbound/outbound traffic. Combine dimensions such as slbid, host, method, and status.

  • Run intelligent health checks at global and slbid levels. Annotate anomalies directly in visualization reports.

Benefits

  • Simple: Activate with one click. No need to handle log collection, storage, computing, or visualization separately.

  • Scalable: Access log volume grows with CLB PVs. CloudLens for CLB supports custom pre-aggregation to calculate metrics in real time, reducing data volume by orders of magnitude and improving query speed.

  • Real-time: SLS analyzes and processes logs within seconds of generation, supporting DevOps, monitoring, and alerting scenarios.

  • Flexible: Enable or disable access logging per CLB instance, set custom log retention periods, and dynamically scale Logstore capacity.

  • Intelligent: AIOps algorithms from DAMO Academy provide automatic health checks for CLB metrics, helping you identify and locate issues faster.

Assets

All assets are stored in your selected project:

  • Logstore

    • The access log Logstore, which you create, stores CLB access logs.

    • The configuration audit log Logstore, which you create, stores configuration audit logs.

    • The CloudMonitor event Logstore, which you create, stores CloudMonitor events.

    • The health check result Logstore stores health check results. When you enable access log ingestion, a Logstore named access_log_logstore_name-metrics-result is automatically created.

    Warning

    • Do not delete these Logstores. Deleting them stops SLS log collection.

    • Do not delete field indexes in the access log Logstore. Removing them causes metric transformation failures.

  • Metricstore

    Stores aggregated metric data. When you enable access log ingestion, a Metricstore named access_log_logstore_name-metrics is automatically created.

    Note

    Aggregated metrics are much smaller than raw access logs, making the Metricstore ideal for long-term storage.

  • Aggregation rules

    Rule name

    Aggregation time granularity

    Aggregation dimension

    Generated metric name

    total

    10 seconds

    total

    • pv

    • body_bytes_sent_avg

    • body_bytes_sent_sum

    • request_length_avg

    • request_length_sum

    • upstream_response_time_avg

    • upstream_response_time_p50

    • upstream_response_time_p90

    • upstream_response_time_p99

    • request_time_avg

    • request_time_p50

    • request_time_p90

    • request_time_p99

    slbid

    10 seconds

    slbid

    • pv:slb

    • body_bytes_sent_avg:slb

    • body_bytes_sent_sum:slb

    • request_length_avg:slb

    • request_length_sum:slb

    • upstream_response_time_avg:slb

    • upstream_response_time_p50:slb

    • upstream_response_time_p90:slb

    • upstream_response_time_p99:slb

    • request_time_avg:slb

    • request_time_p50:slb

    • request_time_p90:slb

    • request_time_p99:slb

    slbid_host_status

    10 seconds

    slbid+host+status

    • pv:slbid:host:status

    • body_bytes_sent_avg:slbid:host:status

    • body_bytes_sent_sum:slbid:host:status

    • request_length_avg:slbid:host:status

    • request_length_sum:slbid:host:status

    • upstream_response_time_avg:slbid:host:status

    • upstream_response_time_p50:slbid:host:status

    • upstream_response_time_p90:slbid:host:status

    • upstream_response_time_p99:slbid:host:status

    • request_time_avg:slbid:host:status

    • request_time_p50:slbid:host:status

    • request_time_p90:slbid:host:status

    • request_time_p99:slbid:host:status

    slbid+host+status+request_method+upstream_status+url

    10 seconds

    slbid+host+status+request_method+upstream_status+url

    • pv:slbid:host:status:method:upstream_status

    • body_bytes_sent_avg:slbid:host:status:method:upstream_status

    • body_bytes_sent_sum:slbid:host:status:method:upstream_status

    • request_length_avg:slbid:host:status:method:upstream_status

    • request_length_sum:slbid:host:status:method:upstream_status

    • upstream_response_time_avg:slbid:host:status:method:upstream_status

    • upstream_response_time_p50:slbid:host:status:method:upstream_status

    • upstream_response_time_p90:slbid:host:status:method:upstream_status

    • upstream_response_time_p99:slbid:host:status:method:upstream_status

    • request_time_avg:slbid:host:status:method:upstream_status

    • request_time_p50:slbid:host:status:method:upstream_status

    • request_time_p90:slbid:host:status:method:upstream_status

    • request_time_p99:slbid:host:status:method:upstream_status

  • Health check rules

    Rule name

    Enabling status

    Health check algorithm

    Health check metric

    slb-patrol-total

    Enabled by default

    Time2Graph

    • pv

    • body_bytes_sent_avg

    • body_bytes_sent_sum

    • request_length_avg

    • request_length_sum

    • upstream_response_time_avg

    • upstream_response_time_p50

    • upstream_response_time_p90

    • upstream_response_time_p99

    • request_time_avg

    • request_time_p50

    • request_time_p90

    • request_time_p99

    slb-patrol-slb

    Enabled by default

    Time2Graph

    • pv:slb

    • body_bytes_sent_avg:slb

    • body_bytes_sent_sum:slb

    • request_length_avg:slb

    • request_length_sum:slb

    • upstream_response_time_avg:slb

    • upstream_response_time_p50:slb

    • upstream_response_time_p90:slb

    • upstream_response_time_p99:slb

    • request_time_avg:slb

    • request_time_p50:slb

    • request_time_p90:slb

    • request_time_p99:slb

    slb-patrol-slbid_host_status

    Disabled by default

    Time2Graph

    • pv:slbid:host:status

    • body_bytes_sent_avg:slbid:host:status

    • body_bytes_sent_sum:slbid:host:status

    • request_length_avg:slbid:host:status

    • request_length_sum:slbid:host:status

    • upstream_response_time_avg:slbid:host:status

    • upstream_response_time_p50:slbid:host:status

    • upstream_response_time_p90:slbid:host:status

    • upstream_response_time_p99:slbid:host:status

    • request_time_avg:slbid:host:status

    • request_time_p50:slbid:host:status

    • request_time_p90:slbid:host:status

    • request_time_p99:slbid:host:status

    slb-patrol-slbid_host_status_request_method_upstream_status

    Disabled by default

    Time2Graph

    • pv:slbid:host:status:method:upstream_status

    • body_bytes_sent_avg:slbid:host:status:method:upstream_status

    • body_bytes_sent_sum:slbid:host:status:method:upstream_status

    • request_length_avg:slbid:host:status:method:upstream_status

    • request_length_sum:slbid:host:status:method:upstream_status

    • upstream_response_time_avg:slbid:host:status:method:upstream_status

    • upstream_response_time_p50:slbid:host:status:method:upstream_status

    • upstream_response_time_p90:slbid:host:status:method:upstream_status

    • upstream_response_time_p99:slbid:host:status:method:upstream_status

    • request_time_avg:slbid:host:status:method:upstream_status

    • request_time_p50:slbid:host:status:method:upstream_status

    • request_time_p90:slbid:host:status:method:upstream_status

    • request_time_p99:slbid:host:status:method:upstream_status

  • Dedicated dashboards

    Dashboard name

    Associated Logstore or Metricstore

    Description

    Monitoring Overview

    access_log_logstore_name-metrics

    Overall CLB monitoring: core indicators, error codes, traffic, anomalies, PVs, and success rate.

    Monitoring Center

    • access_log_logstore_name-metrics

    • access_log_logstore_name

    Real-time CLB monitoring: PVs, success rate, latency (average/P50/P90/P99), 4xx codes, status distribution, traffic, and top hosts/URLs/backends by requests, latency, and failure rate.

    Second-level Monitoring

    access_log_logstore_name

    Second-level CLB metrics: QPS, access/upstream latency, success rate, request/response traffic, and status code breakdown (2xx/3xx/error) for both client and upstream.

    Instance Health Check

    • access_log_logstore_name-metrics

    • access_log_logstore_name-metrics-result

    ML-based anomaly detection for CLB instances. Shows total anomalies, high-severity anomalies, severity distribution, medium-severity anomalies, low-severity anomalies, anomaly list, and anomaly events.

    Access Overview

    access_log_logstore_name

    CLB access overview: PV/UV trends (day-over-day, week-over-week), distribution, today's PVs, 7-day PVs, top 10 provinces, mobile client percentage, and top 10 hosts/user agents/IPs.

Billing

  • Server Load Balancer does not charge additional fees for the log management feature.

  • After you enable CLB access log ingestion, SLS charges for storage, read traffic, requests, data transformation, and data shipping. Billable items of the pay-by-feature billing method.

Limits

  • Access log collection requires CLB instances with Layer 7 listeners.

  • The SLS project and the CLB instance must be in the same region.

  • CloudLens for CLB is available in the following regions.

    Cloud type

    Region

    Public cloud

    China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), Japan (Tokyo), US (Silicon Valley), US (Virginia), Germany (Frankfurt), UK (London), and UAE (Dubai)

    Finance Cloud

    China (Hangzhou) Finance Cloud, China (Shanghai) Finance Cloud, China (Shenzhen) Finance Cloud

Notes

Warning

The CloudLens feature requires at least one project to exist under your Alibaba Cloud account.

When you enable and use the CloudLens feature, Simple Log Service checks whether a project exists under your account based on the following logic.

Detection logic

  1. When you enable the CloudLens feature for the first time, Simple Log Service checks whether a project exists under your Alibaba Cloud account. If no project exists, a project named aliyun-product-data-Alibaba Cloud account ID-cn-heyuan is created in the China (Heyuan) region.

  2. After you enable the CloudLens feature and navigate to the CloudLens page, Simple Log Service checks only whether a project exists under your Alibaba Cloud account. It does not automatically create a project in the China (Heyuan) region. You can manually create a project. For more information about how to create a project, see Manage projects.

Delete a project

  • To delete the aliyun-product-data-Alibaba Cloud account ID-cn-heyuan project, open Cloud Shell and run the following command. Replace Alibaba Cloud account ID with your actual account ID.

    aliyunlog log delete_project --project_name=aliyun-product-data-Alibaba Cloud account ID-cn-heyuan --region-endpoint=cn-heyuan.log.aliyuncs.com

  • For more information about how to delete other projects and Logstores, see Manage Logstores and Manage projects.

Previous：Log fieldsNext：Authorize a RAM user to operate CloudLens for CLB