FAQ about CloudLens for SLS

What data does CloudLens for SLS have, and is it charged?

After you enable CloudLens for SLS, two types of logs are saved for the destination project. By default, the logs are stored in a project named log-service-{Alibaba Cloud account ID}-{region}, where region is the region of the project:

• Detailed logs (charged): Stored in a Logstore named internal-operation_log, these logs cover all resource creation, modification, update, and deletion operations in the project, as well as data read and write operations.

• operation logs (free of charge): Important logs and job operation logs, stored in a Logstore named internal-diagnostic_log. These include consumer group consumption latency logs per Logstore; Logtail/LoongCollector error, heartbeat, and statistics logs; and operational metrics and logs for tasks such as data transformation (new version), scheduled SQL, data import, and data shipping (new version).

The collection and monitoring feature requires you to enable Operation logs. The storage, query, and analysis of Operation logs are free of charge. For more information, see Billing.

How do I enable and find the operation logs of a project to configure alerts?

If no data is displayed on the CloudLens for SLS collection and monitoring interface, see Enable the log collection feature to enable the required operation logs.

If you have enabled operation logs for the destination project but cannot find its storage location to configure alerts, go to the CloudLens for SLS home page and click Instances. Find the project that you want to query and hover over the right side of the project to view its storage location, and click to navigate to it.

The pop-up shows information such as the target Logstore, region, retention period, and matching rule. Click the copy icon next to the target Logstore name to copy it.

Why do I see an error and no report data when I access CloudLens for SLS monitoring?

If the operation logs for the destination project have been enabled for a long time, the index may be outdated. Click Reset Indexes to update it, wait a moment, and then run the query again.

In the left-side navigation pane, choose Report Center > Collection and Monitoring. The reset indexes button is in the upper-right corner of the page.

Resetting the index affects only new data. Existing data remains unchanged. If necessary, you can reindex the data in the Logstore that stores the operation logs.