All Products
Search
Document Center

Simple Log Service:Usage notes

Last Updated:Dec 23, 2024

Simple Log Service and Microservice Engine (MSE) jointly launch the log delivery feature for gateways. You can use the feature to record the access logs of your gateways. This helps you analyze the behavior and geographical locations of client users and troubleshoot issues at the earliest opportunity. This topic describes the assets, billing, and limits of the log delivery feature.

Assets

  • Project and Logstore

    Important
    • Before you disable log delivery, do not delete the related Simple Log Service projects and Logstores. Otherwise, the collected logs are deleted and subsequent logs cannot be delivered to Simple Log Service.

    • If you have enabled the pay-by-ingested-data billing mode, Simple 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, modify the configurations of the Logstore. For more information, see Manage a logstore.

    • If you use the default project when you enable the log delivery feature, Simple Log Service creates a project named aliyun-product-data-<Alibaba Cloud account ID>-<Region ID> and a dedicated Logstore named mse_gw_access_log.

    • If you select an existing project when you enable the log delivery feature, Simple Log Service creates a dedicated Logstore named mse_gw_access_log in the project.

  • Dedicated dashboards

    After you enable the log delivery feature, Simple Log Service generates five dashboards by default.

    Dashboard

    Description

    MSE Ingress Monitor

    Displays statistics such as page views (PVs), unique visitors (UVs), inbound traffic, outbound traffic, status code distribution, request success rate, average latency, and failure rate.

    MSE Ingress Access

    Displays statistics such as the PVs of the current day, UVs of the current day, PV distribution, UV distribution, predicted PVs, predicted UVs, top 10 request provinces, top 10 request cities, percentage of mobile users, percentages of Android and iOS users, top 10 visited user agents, top 10 request hosts, and top 10 request URLs.

    MSE Ingress Detail

    Displays statistics such as error log details, service-level monitoring data, and route-level details.

    MSE Ingress TOP

    Displays statistics such as top 10 service requests, top 10 service failure rate, top 10 service latency, top 10 service traffic, top request URLs, and top request services.

    MSE Ingress Intance Detail

    Displays statistics such as the distribution of request gateways, failure rate, request latency, and top request instances.

Billing

  • You are not charged for the log delivery feature of MSE.

  • If the billing mode of the related Logstore is pay-by-feature, you are charged based on the storage usage, read traffic, number of requests, data transformation, and data shipping after MSE access logs are delivered to Simple Log Service. For more information, see Billable items of pay-by-feature.

  • If the billing mode of the related Logstore is pay-by-ingested-data, you are charged based on the storage usage and read traffic over the Internet after MSE access logs are delivered to Simple Log Service. For more information, see Billable items of pay-by-ingested-data.

Limits

  • You can write only MSE access logs to the dedicated Logstore. You cannot modify the indexes of the dedicated Logstore. No limits are imposed for features such as query, analysis, and alerting.

  • The gateway for which you enable the log delivery feature and the specified Simple Log Service project must reside in the same region.