Service logs

更新时间:
复制 MD 格式

SLS records operation logs and other log data for each project, and provides dashboards for real-time monitoring and O&M analysis.

Default configurations

Default configuration item

Configuration details

Logstore

Two dedicated Logstores are created by default:

  • internal-diagnostic_log: Records consumer group latency, Logtail heartbeat logs, and task operational logs, distinguished by topic. Retention: 30 days (fixed). Free of charge.

  • internal-operation_log: Records one log entry per request. Default retention: 30 days (modifiable). Billed the same as a standard Logstore.

Service log types.

Note
  • Service log Logstores accept only SLS-generated logs. Queries, statistics, alerting, and real-time consumption work normally.

  • Service log data follows standard SLS billing. Pay-by-feature billing items.

Region

  • Select Automatic Creation (Recommended) to create a Project in the same region.

  • Or select an existing Project in the same region from the drop-down list.

Shard

Each Logstore has two shards by default with Automatic sharding enabled.

Log storage period

Default retention is 30 days, modifiable for all Logstores except internal-diagnostic_log. Manage Logstores.

Index

Enabled by default. To disable, go to Query & Analysis > Query & Analysis Properties and turn off indexing.

Dashboard

Created by default:

  • Detailed logs

    • Access traffic monitoring

    • Access anomaly monitoring

  • Critical logs

    • Consumer group monitoring

    • Overall Logtail status

    • Logtail file collection monitoring

    • Logtail anomaly monitoring

Service log dashboards.

Scenarios

  • Determine if shard writes and consumption are balanced

    Use the predefined dashboards to compare shard write and consumption trends.

    Logstores in a project may share shards. Add a Logstore filter to view per-Logstore write distribution.

  • Monitor API request status

    Each API call generates an entry in internal-operation_log. Failed requests return a Status code greater than 200 (for example, 404). Monitor entries where Status exceeds 200 to detect anomalies.

  • Check Logtail status

    Enabling critical logs creates three Logtail dashboards by default: Overall Logtail status, Logtail file collection monitoring, and Logtail anomaly monitoring.