Log Service and Enterprise Distributed Application Service (EDAS) jointly launch the log collection feature. You can use the feature to deliver business logs and container stdout and stderr of applications that are deployed in Container Service for Kubernetes (ACK) clusters to Log Service for query and analysis. This topic describes the assets and billing of the log collection feature.
Assets
Project and Logstore
ImportantBefore you disable the log collection feature, do not delete the projects or Logstores that are related to EDAS logs. Otherwise, EDAS logs cannot be sent to Log Service.
If you have enabled the pay-by-ingested-data billing mode, Log Service creates a dedicated Logstore that uses the pay-by-ingested-data billing mode by default. If you want to switch the billing mode from pay-by-ingested-data to pay-by-feature, you can modify the configuration of the Logstore. For more information, see Manage a Logstore.
After you enable the log collection feature, EDAS uses the project that is specified when you create your Kubernetes cluster and creates a custom Logstore in the project.
Dedicated dashboard
After you enable the feature, Log Service does not generate dedicated dashboards. You can create a custom dashboard to visualize query results. For more information, see Create a dashboard.
Billing
You are not charged for log collection on the EDAS side.
If your Logstore uses the pay-by-feature billing mode, you are charged for storage, read traffic, number of requests, data transformation, and data shipping after the logs are collected from EDAS to Log Service. The fees are included in the bills of Log Service. For more information, see Billable items of pay-by-feature.
If your Logstore uses the pay-by-ingested-data billing mode, you are charged only for read traffic over the Internet after the logs are collected from EDAS to Log Service. The fees are included in the bills of Log Service. For more information, see Billable items of pay-by-ingested-data.