All Products
Search

This Product

    Microservices Engine:Important logs

    Document Center

    Microservices Engine:Important logs

    Last Updated:Apr 15, 2025

    You can view logs to quickly check the running status of a single server to troubleshoot issues. This topic describes the important logs that are provided by Microservices Engine (MSE). The logs are applicable to all applications for which MSE application protection is enabled.

    Important

    • MSE agent versions earlier than 4.3.0: ${BaseDir}=${user_home}/logs/csp.

    • MSE agent version 4.3.0 and later: ${BaseDir}=/home/admin/.opt/AliyunJavaAgent/logs/sentinel.

    • You can query the MSE agent version from the node details of your application.

    File

    Path

    Description

    Second-level monitoring logs

    ${BaseDir}/${app_name}-metrics.log

    Second-level monitoring logs are generated for resources. You can view the running status of resources in the logs.

    Blocking details logs

    ${BaseDir}/sentinel-block.log

    After a rule takes effect, requests that meet the rules are blocked and relevant logs are generated.

    Business logs

    ${BaseDir}/sentinel-record.log.${Current date}

    Business logs record the push, reception, and processing of rules and resource calls. The logs are useful for troubleshooting.

    Second-level monitoring logs

    Second-level monitoring logs are generated for all resources and saved in the ${app_name}-metrics.log file in the ${BaseDir} path. Each row records the metric data of a resource in one second. The following data shows an example.

    1718765870000|2024-06-19 02:57:50|/flow|30|5|30|10|13|0|1|1|IN

    1. 1718765870000: the timestamp.

    2. 2024-06-19 02:57:50: the formatted timestamp.

    3. /flow: the resource name.

    4. 30: the passed queries per second (QPS). The value represents the number of times the resource is passed in one second. The value also indicates the number of checks that are passed based on Sentinel rules.

    5. 5: the rejected QPS. The value represents the number of times a resource is blocked in one second.

    6. 30: the completed QPS. The value represents the number of times calls of a resource are made in one second, including the successful and failed calls.

    7. 10: the abnormal QPS. The value represents the number of processing exceptions of a resource in one second.

    8. 13: the average response time (RT) of a resource.

    9. 0: You do not need to pay attention to this value.

    10. 1: the parallelism. The value represents the number of requests that are being processed by a resource but their calls are not completed.

    11. 1: You do not need to pay attention to this value.

    12. IN/OUT: the server request (IN) or client request (OUT) of the console.

    Blocking details logs

    Regardless of throttling, degradation, or system protection, their second-level blocking details logs are stored in the sentinel-block.log file in the ${BaseDir} path. Each row records the denial-related metric data of a resource in one second. The following sample data shows the data format. 

    2024-06-19 03:13:44|1|/a,ConcurrencyLimitException,default,origin,26133,1718766824000|1,0,0
2024-06-19 03:13:45|1|/flow,FlowException,default,origin,33593,1718766825000|6,0,0

    1. 22024-06-19 03:13:44: the formatted timestamp.

    2. 1: the serial number. You do not need to pay attention to this value.

    3. /a: the resource name.

    4. XXXException: the blocking type. FlowException indicates interface throttling. ConcurrencyLimitException indicates concurrency isolation. WebFlowException indicates hot parameter protection (HTTP). ParamFlowException indicates hot parameter protection (RPC). DegradeException indicates circuit breaking or degradation.

    5. default: You do not need to pay attention to this value.

    6. origin: You do not need to pay attention to this value.

    7. 26133: the ID of the rule for triggering throttling.

    8. 1718766824000: the timestamp.

    9. 1,0,0: 1 indicates the number of throttling or degradation occurrences within one second. A value of 0 has no meaning and can be ignored.

    Business Logs

    Business logs are stored in the sentinel-record.log.xxx file in the ${BaseDir} path. The logs record information about pushing, reception, and processing of rules.