All Products
Search
Document Center

Microservices Engine:Release notes for the MSE agent

Last Updated:Apr 30, 2024

This topic describes the release notes for the Microservices Engine (MSE) agent.

Note

MSE and ARMS share the same Java agent. In this topic, only the release notes for the MSE agent are provided. For the release notes for ARMS agent, see Release notes of the ARMS agent for Java.

2024

Version

Release date

Description

3.2.4

2024-03-28

  • The custom event tracking feature is supported for traffic protection provided by Microservices Governance.

  • Spring Boot 3.0 to 3.2 are supported in Microservice Governance.

  • JDK 21 is supported in Microservice Governance.

  • Dubbo 3.x is supported in Microservice Governance.

2023

Version

Release date

Description

3.1.4

2023-12-25

  • The performance issue in the MSE logic is fixed.

  • The following issue is fixed: If the value of Related is changed from false to true, the readiness probe cannot pass the check.

  • The following issue is fixed: Delayed registration is invalid for Eureka instances.

  • In scenarios where only the MSE features are enabled, Application Real-Time Monitoring Service (ARMS) Span, metrics, and metadata are no longer collected.

  • The filters of Zuul gateways or Spring Cloud Gateways are used instead of Tomcat to parse request parameters and bodies.

  • The fault tolerance logic is added to the end-to-end canary release capability. If the trace is empty, requests are sent to the base environment rather than any other environments.

  • Data of the CPU utilization metric of Microservices Governance Enterprise Edition is collected by Sentinel.

3.0.7

2023-11-18

  • JDK 1.6 and 1.7 are no longer supported in MSE agent V3.0.7 and later.

  • The conflicts between the service authentication switch and other configuration items are fixed.

  • The type of the agent thread pool is set to static final to help you obtain the ownership of the thread pool.

  • If MSE is not enabled for the agent, the MSE logic is not executed.

  • For the two WebInterceptors that are used for traffic protection, their resource names are aligned with the behavior by default, and the interface names include the context-path prefix.

  • The microservices insight feature provided by Microservices Governance no longer reports data to the server. The agent stores related data to local logs. You can manually collect the data based on your business requirements.

  • The following issue is fixed for traffic protection: An error is reported when FeignClientBuilder creates a FeignClient in the forType mode.

  • Custom remote procedure call (RPC) behavior is supported for traffic protection.

  • The SentinelWebInterceptor component is used first during the traffic protection process to obtain accurate throttling data.

  • The SentinelWebInterceptor component introduced by the agent is used as the starter for traffic protection when the starter ingestion mechanism becomes invalid.

2.9.2

2023-09-09

  • Custom RPC behavior is supported for traffic protection.

  • The SentinelWebInterceptor component is used first during the traffic protection process.

  • The SentinelWebInterceptor component introduced by the agent is used as the starter for traffic protection when the starter ingestion mechanism becomes invalid.

2.9.1.2

2023-08-03

  • The following issue is fixed: Traffic loads are not balanced when Spring Cloud Ribbon is used.

  • The alicloud_service_tag labels or annotations can be used to tag nodes.

  • Microservices Governance is available on China East 1 Finance.

  • If MSE is not activated, MSE-related logic is not initialized.

  • The cache issue of GetLocalV4Ip is fixed.

  • The following issue is fixed: Traffic requests fail when MSE Enterprise Edition uses both Spring Cloud Gateway and open source SCA Sentinel.

  • The following issue is fixed: Only the fallback method is supported in the Feign framework for traffic protection.

  • The following issue is fixed: The file timestamps of the labels and annotations are inconsistent, which causes continuous re-registration.

  • The following issue is fixed: asynchronous trace data is occasionally lost when the Reactor framework is used.

2.9.0

2023-07-13

  • Traffic protection supports the frameworks of Zuul gateways and Spring Cloud Gateways.

  • MSE supports persistent service discovery.

  • Canary release and tag-based routing support Dubbo 3.x.

  • End-to-end canary release rule matching of HTTP bodies is supported.

  • The performance of graceful start and shutdown in MSE is improved.

2.8.3

2023-03-31

  • JDK 11 and JDK 17 are supported.

  • MSE allows applications in different environments to access different namespaces. This way, applications in different environments such as development environments, test environments, and online environments can be isolated from each other.

  • MSE supports traffic protection.

  • The microservices insight feature is completely released and the graceful start and shutdown and end-to-end canary release features are improved in terms of observability.

  • Microservices Governance provided by MSE supports Consul registries.

  • End-to-end canary release supports Consul and Undertow.

2022

Version

Release date

Description

2.7.3.5

2022-07-27

  • Canary release for RocketMQ messages is supported.

  • OpenSergo registry tagging and canary release of MSE cloud-native gateways are supported.