This topic provides the change description on Microservices Engine (MSE) agent 4.3.x.
Usage notes of MSE agent 4.3.x
To ensure compatibility with open source Sentinel and improve the agent stability, MSE optimizes the implementation of traffic protection in version 4.3.x and maintains feature compatibility with earlier versions. The following changes require attention from users who have used the corresponding features.
Users who have collected local metric logs
The MSE metric log path has changed from ～/logs/csp/ to /home/admin/.opt/AliyunJavaAgent/logs/sentinel/. In Elastic Compute Service (ECS) environments, the MSE metric log path is changed to Agent installation directory/logs/sentinel. We recommend that you add the new log path to your Logtail collection configuration to collect relevant logs as expected. For more information, see Report MSE traffic protection metrics to Simple Log Service.
Users who have imported Sentinel or Spring Cloud Alibaba dependencies
Version 4.3.x is compatible with Sentinel and Spring Cloud Alibaba dependencies. After you upgrade the MSE agent to 4.3.x, interfaces with the prefix SENTINEL: are added to custom interfaces. The added interfaces are generated by Sentinel or Spring Cloud Alibaba dependencies. This does not adversely affect the original interfaces and rules of MSE. You can determine whether to remove these dependencies.
Users who have imported Sentinel dependencies to implement custom interfaces
For users who have added custom interfaces based on MSE-related documentation, no points need to be noted.
For users who have introduced open source adapters for tracking or do not set ResourceType to COMMON for resources during the creation of custom interfaces, these resources belong to the custom interfaces, EntryType is set to INTERNAL for these resources, and the
SENTINEL:prefix is added to resource names. Related rules need to be modified accordingly.