Layer 7 access logs for Classic Load Balancer (CLB)

Simple Log Service and Classic Load Balancer (CLB) jointly launch the Layer 7 access log feature to record the details of all requests sent to CLB, including the request time, client IP address, latency, request path, and server response. You can analyze client behavior, geographic distribution, and troubleshoot issues based on the access logs.

Assets

Custom Simple Log Service project and Logstore
- Indexing is enabled by default for the Logstore, and indexes are configured for some fields.
  
  You can modify the indexes. New indexes take effect only on data that is written after the modification. You can also reindex historical data. For more information, see Reindex logs for a Logstore.
- By default, logs are stored permanently in the Logstore. You can also modify the log storage period. For more information, see Manage a Logstore.
Important
- Before you disable the Layer 7 access log feature, do not delete the associated Simple Log Service project or Logstore. Otherwise, logs cannot be pushed to Simple Log Service.
- When you create a custom Logstore, the billable items vary based on the billing method. For more information, see Billable items.

Dedicated dashboards

Two dashboards are generated by default.

Note

We recommend that you do not modify the dedicated dashboards because they may be upgraded or updated at any time. You can create a custom dashboard to visualize query results. For more information, see Create a dashboard.

Dashboard	Description
slb_layer7_operation_center_cn	Shows overall CLB operational statistics, including page views (PVs), unique visitors (UVs), request success rate, request traffic, and response traffic.
slb_layer7_access_center_cn	Shows request details for CLB, including PV distribution by client, PV trends of request methods and status codes, top clients, and request traffic topology.

Billing

Currently, no additional fees are charged for the CLB Log Management feature.
If the Logstore uses the pay-by-feature billing method, you are charged for storage space, read traffic, the number of requests, data transformation, and data shipping after Simple Log Service collects the Layer 7 access logs. For more information, see Billable items for the pay-by-feature method.
If the Logstore uses the pay-by-ingested-data billing method, you are charged based on the amount of raw data ingested after the Layer 7 access logs are collected. For more information, see Billable items for the pay-by-ingested-data method.

Limits

The Layer 7 access log feature is available only for CLB instances that have a Layer 7 listener configured.
The CLB instance must reside in the same region as the Simple Log Service project.

Benefits

Ease of use: Frees developers and O&M personnel from tedious log processing, allowing them to focus on business development and technical research.
Immense processing capabilities: As PVs grow, CLB access logs increase rapidly. Simple Log Service analyzes 100 million logs within 1 second and is more cost-effective than open source solutions.
Real-time processing capabilities: For scenarios such as DevOps, monitoring, and alerting, CLB integrates with the big data computing capabilities of Simple Log Service to analyze and process real-time logs in seconds.

Important
Log latency is less than 3 minutes in 99.9% of cases.
Elasticity: You can enable or disable the access log feature for each CLB instance and set a custom log storage period. The Logstore capacity scales dynamically to meet business growth requirements.