The service log feature in Log Service helps you record log data about the operations that are performed in a project. The feature also provides dashboards that allow you to analyze data from multiple dimensions. You can use this feature to view the service status of Log Service in real time and improve O&M efficiency.

Limits

  • The automatically created Logstores are used to store only the logs generated by Log Service. You cannot write other data to the Logstores. However, you can perform other operations on the automatically created Logstores. For example, you can search and analyze data in the Logstores, configure alerts, or use the Logstore data for streaming consumption.

  • If you enable the service log feature as a RAM user, you must use your Alibaba Cloud account to grant the RAM user relevant permissions.

  • After you enable the service log feature for a project, you can store the relevant project logs only in another project that belongs to the same region.

  • You are charged for the log data recorded by the service log feature based on the pay-as-you-go method. Free resource quotas are provided on a monthly basis. For more information, see Pay-as-you-go.

  • To disable the service log feature, you can clear the selected log types in the Service Logs section. After you disable the feature, service logs are not recorded. However, historical logs are not automatically deleted. If you do not delete the data manually, a small amount of fee may be incurred. If you want to delete historical logs, you can delete the Logstores where the logs are stored.

Default configurations

Table 1. Default configurations
Default configuration item Description
Logstore Two Logstores are automatically created for the project that you specify to store service logs. Log data generated under the project for which the service log feature is enabled is classified and stored in one of the following Logstores:
  • internal-operation_log: stores operations log data. A log entry corresponds to an API request. By default, log data in the Logstore is retained for 30 days. The Logstore is charged as a common Logstore.
  • internal-diagnostic_log: stores metering logs, consumption delay logs of consumer groups, and Logtail-related logs. The logs are classified by topic. By default, log data in the Logstore is retained for 30 days. The Logstore is free of charge.
For more information about log types and fields, see Log types.
Region
  • If you select Automatic creation (recommended), a project is automatically created in the same region as the project for which the service log feature is enabled.
  • If you specify a project to store logs of the project for which the service log feature is enabled, the specified project must reside in the same region as the project.
Shard By default, two shards are created for each Logstore and the automatic sharding switch is turned on.
Log retention period By default, log data is retained for 30 days. You can modify the retention period. For more information, see Manage a Logstore.
Index By default, the index feature is enabled for all collected log data. If you do not need to search and analyze data or configure alerts, you can disable the index feature on the Search & Analysis page of the Logstores.
Dashboard The following five dashboards are automatically created:
  • Operation statistics dashboard
  • Metering statistics dashboard
  • Logtail log collection statistics dashboard
  • Logtail exception monitoring dashboard
  • Consumer group monitoring dashboard
For more information about dashboards, see Service log dashboards.

Scenarios

  • Check whether data is evenly written and consumed among shards

    You can view the data write and consumption trends of shards in a dashboard. In this way, you can check whether data is written or consumed evenly among shards.

    Multiple Logstores under a project may share the same shards. To view the data writes to multiple shards of a Logstore, you can add filtering conditions on the dashboard to filter Logstores.

  • Monitor API request status

    You can call API operations to write log data, consume log data, and create projects or Logstores. A log entry is generated in the internal-operation_log Logstore when an operation is performed. If an API request fails, the value of the Status field in the generated log entry is an integer greater than 200, for example, 404. You can monitor API requests by viewing the number of log entries whose Status field value is greater than 200.

  • View Logtail status

    After you activate the service log feature, two dashboards are automatically created for Logtail. One dashboard monitors Logtail exceptions and the other analyzes data collected by Logtail. The exception monitoring dashboard helps you monitor Logtail exceptions such as regular expression mismatches and log data parsing failures.