Docs

Torch Log Service

Monitor Log Service

View cloud monitoring data

TLS is integrated with cloud monitoring. During daily operations, you can view various billing-related monitoring metrics directly in the TLS console or the cloud monitoring console and monitor resource usage in real time. This topic shows TLS monitoring metrics and explains how to view them.

Prerequisites

Cloud monitoring service is enabled; cross-service access authorization is completed as prompted on the page; cloud monitoring is granted with permission to access TLS data. For more information about cloud monitoring, see Cloud monitoring service.

Notice

The units in the monitoring metric table are base units. For the actual units used for each metric, refer to cloud monitoring console. The units displayed on the console are adjusted dynamically based on monitoring values and conversion standards. For example, the basic unit for log storage is Byte. If the volume of log storage reaches the level of KiB, GiB, or TiB, the unit displayed on the console may change to KiB, GiB, or TiB.

View monitoring data

You can view monitoring data (resource usage and operational status) in either the TLS console or the Cloud Monitoring console. For detailed information about monitoring data, see Descriptions of monitoring metrics.

View monitoring data in TLS console

On the left navigation bar, select Resource management > Project.

Click the specified project name.

Under the Topic tab from left navigation pane, click the expand button before specified log topic, and then click Cloud Monitoring .

View cloud monitor data.

By default, the page displays monitoring data for this log topic over the past day (showing the trend of total monitor volume within one day).

You can select a specific time range to view the corresponding data.

Supports chart linkage. If this feature is enabled, when the cursor hovers over any chart, other charts will automatically display the monitoring item data values at the same time.

Check monitoring data in Cloud Monitor console.

Click Cloud Service Monitor in the left navigation bar, and select Storage section, and then select TLS.

Select the region in the top navigation bar. The page displays the alarm overview and project list for the selected region.

The alarm overview shows the total number of current alarms, alarms by level, number of alarm policies, and other metrics.

The project list displays each project's name, ID, creation time, and the number of log topics. You can filter projects by name, ID, creation time, or number of log topics to quickly locate your target project.

Click a project name to view its monitoring data.

Select a log topic name on the TLS billing items tab and view the monitoring data.

Tip

By default, the page displays monitoring data for the past one hour. You can select a specific time range to view the corresponding data. You can also enable chart linkage to view the data values of all monitoring metrics at a specific time.

Set an alarm policy in Cloud Monitor

You can use the Cloud Monitor alert feature to track TLS resource usage and prevent abnormal usage from causing unexpected cost increases. After setting up an alarm policy in the Cloud Monitor console, Cloud Monitor will send notifications promptly when the specified resource usage meets the trigger conditions.

Click Cloud product monitoring in the left navigation pane, and then search for and select TLS.

Click Create alarm policy in the upper-right corner of the page.

On the Create alarm policy page, set alarm policy parameters.

For example, you can monitor resources such as internal write traffic, internal read traffic, log shipping traffic, and data transformation traffic using the following configuration. You can set that alert triggers when the average value increases by 50% compared to the previous day. You can also enable Preset trigger conditions to apply system-recommended alert conditions. For detailed parameter configuration, see Create alarm policy.

Click Create.

Descriptions of monitoring metrics

TLS provides the following monitoring data at the topic level for you to review.

Resource usage monitoring data

Monitoring item ID	Monitoring item name	Unit	Measurement dimension (Dimensions)	Description
StandardLogStorage	Log storage	Byte	ResourceID, Topic	The amount of log storage in standard storage (after compression).
ShardNum	Number of shards	Count	ResourceID, Topic	Sum of read/write shards and read-only shards.
StandardIndexStorage	Index storage	Byte	ResourceID, Topic	After log data in standard storage is indexed, the volume of indexed data (uncompressed) is stored.
ReadRequest	Number of read requests	Count	ResourceID, Topic	Number of requests to call the read data interface of TLS Number of requests made by users to TLS read-write interfaces through LogCollector, Open API, or SDK; requests triggered from the console interface are not included.
WriteRequest	Number of write requests	Count	ResourceID, Topic	The number of requests to the TLS write interface. The number of requests users send to the TLS write interface through LogCollector, Open API, or SDK; requests triggered via the console are not included.
InnerReadTraffic	Private network read traffic	Byte	ResourceID, Topic	Downlink traffic generated when accessing the TLS private network domain name. For example, downloading logs or consuming logs via the private network generates private network read traffic. Query and analysis from the console or API does not generate read traffic.
InnerWriteTraffic	Private network write traffic	Byte	ResourceID, Topic	Uplink traffic generated when accessing TLS private network domain name.
PublicReadTraffic	Public network read traffic	Byte	ResourceID, Topic	Downlink traffic generated when accessing TLS public network domain name. For example, downloading logs or consuming logs via public network programs generates public network read traffic, but querying and analyzing logs through the console or API does not generate read traffic.
PublicWriteTraffic	Public network write traffic	Byte	ResourceID, Topic	Outbound traffic generated when accessing the TLS public domain name.
ShipperTraffic	Data shipping traffic	Byte	ResourceID, Topic	Calculated based on the size of shipped data.
ETLProcessedTraffic	Data transformation traffic	Byte	ResourceID, Topic	Calculated based on the volume of data transformed. Data volume refers to the original uncompressed data size.
IndexTraffic	Index traffic	Byte	ResourceID, Topic	The amount of indexed data is calculated when data is indexed or re-indexed. Data volume refers to the original uncompressed data size.
InfrequentStorage	Infrequent access log storage	Byte	ResourceID, Topic	After enabling infrequent storage, this is the log storage volume in infrequent access mode. This refers to the volume of uncompressed raw data.
InfrequentIndexStorage	Infrequent access index storage	Byte	ResourceID, Topic	Amount of indexed data stored after enabling low-frequency storage and indexing the data. Data volume refers to the original uncompressed data size.
InnerWriteOriginTraffic	Internal network original write traffic	Byte	ResourceID, Topic	Uplink raw data traffic after decompression when accessing the access log service's private domain name.
PublicWriteOriginTraffic	External original write traffic	Byte	ResourceID, Topic	Uplink decompressed original data traffic generated when accessing the public domain name of the log service.
StandardTotalStorage	Total storage	Byte	ResourceID, Topic	The sum of the log storage in standard storage (after compression) and the indexed log data in standard storage (uncompressed).
ShardReadOnlyNum	Number of read-only shards	Count	ResourceID, Topic	Number of read-only shards.
ShardReadWriteNum	Number of read-write shards	Count	ResourceID, Topic	Number of read-write shards.

Running status monitoring data

Monitoring item ID	Monitoring item name	Unit	Measurement dimension (Dimensions)	Description
RequestCode400	400 requests	Count	ResourceID, Topic	Number of requests with status code 400.
RequestCode403	403 requests	Count	ResourceID, Topic	Number of requests with status code 403.
RequestCode404	404 requests	Count	ResourceID, Topic	Number of requests with status code 404.
RequestCode429	429 requests	Count	ResourceID, Topic	Number of requests with status code 429.
RequestCode5xx	5xx requests	Count	ResourceID, Topic	Number of requests with status code 5xx.
ConsumerGroupFallBehind_max	Maximum time consumption lags behind	Second	ResourceID, Topic, ConsumerGroupName	The time difference between the current consumption progress and the latest data written in the queue. In a consumer group, this value represents the maximum time lag among all shards.

Last updated: 2026.04.14 16:16:11