Microservices Engine (MSE) agent 4.3.x redesigns the traffic protection layer for better compatibility with open-source Sentinel and improved agent stability. All existing features remain backward-compatible.
Review the following changes to determine whether your setup is affected.
| Change | Impact | Action required |
|---|---|---|
| Metric log path moved | Action required | Update Logtail collection configuration |
SENTINEL: prefix added to interfaces | No action required | Optionally remove Sentinel or Spring Cloud Alibaba dependencies |
| Custom interface behavior change for non-COMMON resources | Action required (conditional) | Modify related rules if applicable |
Metric log path change
Impact: Action required
The metric log path has changed. If you collect local metric logs, update your Logtail collection configuration before or immediately after upgrading the agent. If you do not update the configuration, log collection stops working after the upgrade.
Before:
~/logs/csp/After:
| Environment | New path |
|---|---|
| Default | /home/admin/.opt/AliyunJavaAgent/logs/sentinel/ |
| Elastic Compute Service (ECS) | <agent-installation-directory>/logs/sentinel |
Add the new log path to your Logtail collection configuration to resume log collection. For details, see Report MSE traffic protection metrics to Simple Log Service.
SENTINEL: prefix added to custom interfaces
Impact: No action required
After upgrading to 4.3.x, interfaces prefixed with SENTINEL: appear in the custom interfaces list. These are generated by Sentinel or Spring Cloud Alibaba dependencies in your application and do not affect existing MSE interfaces or rules.
If these additional interfaces are unnecessary, remove the Sentinel or Spring Cloud Alibaba dependencies from your application.
Custom interface behavior for Sentinel-based resources
Impact: Action required (conditional)
This change applies only if you use open-source Sentinel adapters for tracking or create custom interfaces without setting ResourceType to COMMON.
No action needed if you created custom interfaces based on MSE documentation. Those interfaces are unaffected.
Action needed if either of the following is true:
You introduced open-source Sentinel adapters for tracking.
You did not set
ResourceTypetoCOMMONwhen creating custom interfaces.
In these cases, the following changes take effect after the upgrade:
| Property | New behavior |
|---|---|
| Interface category | Resources are classified as custom interfaces |
EntryType | Set to INTERNAL |
| Resource name prefix | SENTINEL: prefix is added |
Update any rules that reference these resources to match the new resource names with the SENTINEL: prefix.