All Products
Search
Document Center

Cloud Monitor:Agent release notes

Last Updated:Sep 08, 2025

This topic provides the release notes for the Application Monitoring agent of Cloud Monitor 2.0.

View the agent version

  1. Log on to the Cloud Monitor 2.0 console, and select a workspace. In the left navigation pane, choose Application Center > O&M and Monitoring > Application Monitoring.

  2. In the top menu bar, click System Administration, and then click the Agent Release History tab.

  3. In the upper-left corner of the page, select the agent language.

    Cloud Monitor 2.0 provides download links for agent packages that are within their support lifecycle (released within the last six months). We recommend that you select the latest agent version for manual installation. For more information about the agent support lifecycle, see Notice on the support lifecycle of the ARMS Application Monitoring agent.

Agent versions

Java agent

Version

Release date

Description

4.4.0

June 6, 2025

  • The following frameworks are supported:

  • Trigger cause labels can be added to JVM garbage collection (GC) metrics.

  • The following issues are fixed:

    • Negative idle connection counts in Druid

    • Tomcat 8 instrumentation activation conflicting with Jakarta dependencies (Tomcat 10 unaffected)

    • DestId and Endpoint retrieval failures in some Dubbo 3.x versions

    • Redisson response size miscalculations

    • SQL capture failures in OpenTracing-wrapped Java Database Connectivity (JDBC) calls

  • Continuous profiling uses statically linked libraries by default to prevent conflicts with dynamic libraries.

4.3.4

May 20, 2025

  • Business tracing capabilities are added.

  • Business parameter extraction now supports more matching logics. For more information, see Create a rule.

  • Connection pool monitoring now supports the tomcat-dbcp and tomcat-jdbc frameworks. For more information, see Thread pool and connection pool monitoring.

  • The issue where the Tomcat thread pool might appear empty has been resolved.

  • The issue where trace IDs in the Mapped Diagnostic Context (MDC) of user logs were overwritten during the use of the log4j framework has been fixed.

  • The issue where scheduled task data was incorrectly filtered after the collection of internal call data without an entry point was disabled has been corrected.

  • An issue causing occasional missing database call data due to dependencies on ShardingSphere has been resolved.

  • The issue where Baggage failed to propagate in certain versions of Dubbo has been fixed.

  • The issue where agent logs related to continuous profiling were mistakenly output to user standard output due to permission issues has been addressed.

  • An issue causing failure during navigation from the ARMS console to query MongoDB details has been resolved.

  • The ARMS agent now filters out ping commands in Lettuce by default.

  • Collection of internal call data without an entry point is now disabled by default.

4.2.5

April 10, 2025

  • Performance issues caused by using the agent v4.x together with the ARMS SDK have been optimized.

  • Performance issues caused by regular expression-based matching in the Lettuce plug-in have been improved.

  • The issue where Redis command parameters recorded by the Lettuce plug-in contained garbled characters has been resolved.

4.2.3

February 24, 2025

  • The issue of incorrect convergence of interfaces caused by SDK initialization failure in Service Mesh scenarios has been fixed.

  • The error occurring during invocation in the coexistence scenario of Lettuce 5.1+ and React 3.5+ has been fixed.

  • The error encountered when invoking Lettuce with the Collect Data from Entry-less Internal Calls switch turned off in versions 5.1+ has been fixed.

  • The probabilistic context leakage issue occurring during downstream calls via Feign in Spring Cloud when calls fail has been fixed.

4.2.2

January 9, 2025

  • The Motan framework is supported.

  • Filtering of internal calls without entry points is supported.

  • The issue of a rare null pointer exception when executing bulk gets in Memcached has been fixed.

  • The problem with the arms_file_desc_open_ratio metric not being collected has been resolved.

  • The error in master-slave request statistics for ShardingSphere 5.2.+ has been corrected.

  • The issue where server-side calls were incorrectly identified as client-side calls in certain Dubbo scenarios has been fixed.

  • The problem of incomplete agent initialization during application startup when the global switch is off, leading to missing data after the switch is turned on, has been addressed.

  • The failure to automatically populate TraceId and SpanId in the ReusableLogEvent scenario has been resolved.

  • CPU overhead has been optimized for scenarios where users provide HTTP services simultaneously through SpringMVC and custom Servlets.

4.1.13

December 10, 2024

  • An extremely rare null pointer issue that occurred under the Undertow scenario has been fixed.

  • A deadlock issue caused by asynchronous context propagation in the JDK 21 virtual threads scenario has been resolved.

  • An out of memory (OOM) error resulting from reading spring-actuator related metrics has been addressed.

  • A low-probability application startup failure issue that occurred when used in conjunction with other agents has been corrected.

4.2.1

December 6, 2024

  • Support for Lindorm databases has been added.

  • Configuration of blacklists based on thread pool usage scenarios and thread pool thread names is now supported. For more information, see Pooled monitoring settings.

  • Instrumentation using public methods of spring-bean (for collecting method stack data from the agent v3.x) has been enabled. For more information, see Agent switch settings.

  • The use of MDC.get("EagleEye-TraceID") has been supported, with this feature being disabled by default. For more information, see Application log association settings.

  • A switch for configuring trace collection has been implemented. For more information, see Agent collection settings.

  • Code diagnostics now supports asynchronous scenarios and is enabled by default. For more information, see Use the code diagnostics feature to diagnose slow traces for Java applications.

  • Filtering for RPC servers, MQ consumers, scheduled tasks, and spans has been supported. For more information, see Interface call settings.

  • Monitoring of GC-related metrics under Z Garbage Collector (ZGC) generational scenarios has been supported.

  • Business parameter extraction now supports extracting parameters from apache-http-client and okhttp requests. For more information, see Extract business parameters.

  • CPU overhead of the dependency reporting feature has been optimized.

  • Due to deadlock risks in the JDK 21 virtual threads scenario, automatic asynchronous context propagation has been disabled by default.

  • Potential compatibility issues in multi-agent scenarios have been fixed.

  • An issue where the spanName was incorrectly set to POST in certain HttpUrlConnection scenarios has been resolved.

  • An extremely rare null pointer issue that occurred under the Undertow scenario has been fixed.

  • Issues with unrecorded exceptions in certain gRPC framework scenarios have been addressed.

  • Unrecorded exceptions in certain Lettuce plug-in scenarios have been fixed.

  • The problem of missing agent version numbers in agent v4.x metrics has been corrected.

  • A low-probability connection failure issue after opening Arthas has been resolved.

  • An issue preventing proper filtering of POST, GET, /*, /** interfaces in the interface list has been fixed.

  • A startup issue caused by repeated creation of TMPDIR by the agent has been resolved.

  • An issue with incorrect GC metric collection when Microservice Engine (MSE) Pro Edition is simultaneously enabled has been fixed.

  • An issue with missing metrics in Kafka batch consumption scenarios has been addressed.

4.1.12

October 10, 2024

  • The issue of incorrect upstream and downstream data in certain interface scenarios has been fixed.

  • The problem of network-related metrics continuously increasing has been resolved.

  • The issue of duplicate recording of exception metrics has been corrected.

  • The problem where custom parameter extraction did not work in certain scenarios has been addressed.

  • Instrumentation for exception constructor methods has been added to support the recording of all exceptions.

4.1.11

September 15, 2024

  • The principle of quantile calculation has been adjusted. For more information, see ARMS metric quantile calculation.

  • The CPU and memory overhead of the agent has been optimized.

  • A limit on the number of spans created by a single call has been added, with the current upper limit set to 10,000.

  • A new strategy selection for extracting thread names in thread pool monitoring has been implemented, with the default value being REPLACE_ALL_DIGITAL (replacing all numeric characters with *), which can be configured as REPLACE_TAIL_DIGITAL (replacing trailing numeric characters with *).

  • Collection of Java virtual machine (JVM) loaded and unloaded class metrics has been added.

  • Support for more flexible data collection configurations, such as quantiles and upstream or downstream data, has been introduced.

  • A probabilistic crash issue caused by memory hotspots has been fixed.

  • An issue where code hotspot traces could not be searched in certain scenarios has been resolved.

  • A problem with span reporting failures due to null pointer exceptions in the Open Notification Service (ONS) plug-in has been corrected.

  • An initialization failure issue with Kafka has been fixed.

  • An OOM error caused by failed stream reading in MongoDB has been addressed.

  • An issue with incorrect parsing of the ARMS_HOST_TAGS environment variable has been resolved.

  • A data reporting interruption issue in thread pool monitoring has been corrected.

  • Several security vulnerabilities have been patched.

4.1.9

July 10, 2024

  • The name of a Serverless Application Engine (SAE) application failed to be changed by adding the arms.AppName parameter. The bug has been fixed.

  • In Lettuce 5.1, spans failed to be compressed after repeated calls. The bug has been fixed.

  • SQL statements failed to be parsed, and database metrics failed to be reported. The bugs have been fixed.

  • Jedis and Lettuce pool monitoring data was missing. The bug has been fixed.

  • Metric reporting was disrupted. The bug has been fixed.

  • ClassLoader enhancement rarely fails, leading to application startup failures. The bug has been fixed.

  • The http.status_code field is added to spans.

  • Crash logs can be automatically collected by using a script.

4.1.8

June 29, 2024

  • SAE applications with outdated versions and the agent v4.x were incompatible. The bug has been fixed.

4.1.7

June 26, 2024

  • The graceful start and shutdown of MSE failed. The bug has been fixed.

4.1.6

June 13, 2024

  • The JFinal and Webex frameworks have been supported.

  • The pull mode of ApsaraMQ for RocketMQ V4.x has been supported.

  • Trace IDs and span IDs can be automatically filled in in logs.

  • Base exceptions have been supported in the exception settings.

  • Original status codes can be recorded in HTTP metrics.

  • Some connection methods of OceanBase and PolarDB are not supported. The bug has been fixed.

  • WebSocket requests were unable to be identified as failed requests. The bug has been fixed.

  • OOM issues in some asynchronous scenarios have been fixed.

4.1.3

May 27, 2024

  • In Apache Tomcat V10.1.0 to V10.1.6, the 404 HTTP status code occurred in requests with cookies. The bug has been fixed.

4.1.1

May 17, 2024

  • The agent v4.1.0 rarely encounters deadlocks. The bug has been fixed.

  • Jedis SQL data was incorrect. The bug has been fixed.

4.1.0

May 15, 2024

  • Compatible with open source services, the agent v4.1.0 was built based on the OpenTelemetry agent for Java. All previous features have been retained.

  • Custom parameters can be extracted. For more information, see Extract business parameters.

  • PolarDB V2, Cassandra, OceanBase, Apache ShenYu, and Spring Schedule have been supported.

  • Automatic asynchronous context pass-through has been supported without the need to configure package names.

  • Custom consumers can be configured for RabbitMQ. Custom consumption methods can be configured for Kafka.

  • The priority of protocol-based pass-through can be configured for applications.

  • Custom thread pool monitoring settings can be configured.

  • Metrics of applications deployed in Alibaba Cloud Container Service for Kubernetes (ACK) clusters were incorrect. The bug has been fixed.

Go agent

Version

Release date

Description

1.7.1

May 15, 2025

  • Provides event reporting, log collection, and download capabilities during crashes.

  • Supports Kratos 2.1.2-2.4.0 and 2.8.5.

  • Fixes the issue where gRPC span creation fails to release parent spans.

  • Resolves delays in Kratos instrumentation caused by custom middleware execution.

  • Fixes ineffective Mux interface filtering.

  • Fixes missing version configuration for the Go log package and slog package.

1.7.0

April 28, 2025

  • Supports instrumentation in K8s informer.

  • Supports injection based on regex matching of function names and class names.

  • Supports instrumentation in Go-zero logs.

  • Adds the ability to specify a whitelist for interface data collection.

  • Supports the Go vendor module mode.

  • Adds filtering for non-UTF-8 strings in OpenTelemetry SDK string values.

  • Supports instrumentation in K8s Controller Runtime.

  • Supports FastHTTP (1.61.0), Kitex (0.13.1), MySQL (1.9.2), Go-elasticsearch (8.18.0), and gRPC (1.72.0).

  • Fixes the issue where requests with empty path are not collected.

  • Fixes the issue where HTTP trace IDs cannot be returned from the server.

  • Fixes the panic caused by EagleEye span ID generation.

  • Fixes the panic caused by empty headers in AMQP instrumentation.

  • Fixes the issue where trace IDs are missing from logs during the use of the Logrus entry method.

  • Fixes the callKind issue in Kafka message reporting.

  • Fixes the file format issue caused by agent compilation.

  • Fixes the trace ID correlation issue in Hertz instrumentation.

1.6.1

March 31, 2025

  • Fixes the issue where Stream does not match when printing fasthttp bodies.

  • Fixes the issue where Mutex and Lock Profiling fails to retrieve data.

  • Fixes the issue where Agent init starts slower than User init.

  • Fixes the issue where HTTP server 4xx metrics are not recognized as errors.

  • Fixes the issue where protobuf causes compilation failure.

  • Supports setting "agent enable" via the ldflags parameter.

  • Supports configuring whether to report data over the public network via environment variables.

  • Supports Redis 9.7.3 and gRPC 1.71.0.

  • Fixes the issue where k8smetadata and ecsmetadata are missing from the metadata.

1.6.0

March 18, 2025

  • Updates Hertz version support to 0.9.6, go-redis version support to 9.7.1, and OpenTelemetry SDK version support to 1.35.0.

  • Supports hiding instrumentation code during debugging.

  • Supports runtime monitoring for CGO, CPU, and stacks.

  • Fixes the issue of incorrect CPU data collection in system monitoring.

  • Fixes the issue where dependency on golang.org/x/net caused custom plug-in compilation failures in the ARMS agent for Go v1.21 and later.

  • Fixes the issue of go build ./... compilation failures.

  • Fixes the issue of incorrect statistics reporting in self-monitoring metrics.

  • Fixes the issue of incorrect start and end times in some plug-ins.

1.5.3

February 28, 2025

  • Updates fasthttp version support to 1.59.0.

  • Fixes the issue with fasthttp headers not being displayed in the JSON format.

  • Supports passing environment variables through LDFLAGS.

  • Fixes the spanKind error in Go Micro Server.

  • Fixes the issue of missing code in HTTP and gRPC request spans.

  • Supports application template configurations.

  • Fixes the issue where GORM and database parameters could not be displayed.

  • Fixes compilation errors caused by absence of the slog package in Go versions earlier than 1.21.

  • Fixes the issue that the Logrus, Go Micro, fasthttp, and Redis plug-in switches require a restart to take effect.

1.5.2

February 17, 2025

  • Supports on-demand full sampling for interfaces.

  • Supports printing fasthttp bodies and headers.

  • Replaces TYPE_IS_ARMS with the ARMS_ENABLE switch.

  • Updates gRPC version support to 1.70.0, Echo version support to 4.13.3, Go client for Elasticsearch version support to 8.17.1, fasthttp version support to 1.58.0, and Function Compute SDK for Go version support to 0.2.11.

  • Fixes the issue with the HTTP Server Body return switch.

  • Fixes the issue of duplicate instrumentation in fasthttp servers.

  • Fixes the issue where the HTTP span status was not set in the case of a 200 response.

  • Fixes the Redis compression issue during full sampling of error interfaces and slow interfaces.

  • Fixes the issue with navigation from the Database page to Trace Explorer.

1.5.1

January 23, 2025

  • Supports MongoDB 1.17.1.

  • Supports printing HTTP request headers and response headers.

  • Fixes the issue where Thrift instrumentation fails.

  • Fixes the problem with OSS profiling data push related to x509.

  • Fixes the Redis non-UTF-8 issue.

  • Fixes the potential panic caused by the Convergence Sampler.

  • Fixes the conflict between Logrus instrumentation and user instrumentation.

  • Updates support for OpenTelemetry SDK to version 1.34.0.

  • Supports starting the agent functionality through a configuration file.

1.5.0

January 14, 2025

  • Fixes the issue where gRPC timeout configurations do not take effect.

  • Fixes the problem with RocketMQ not recording "out.ids", causing trace navigation to fail.

  • Fixes the issue in Redis v9 where the "err" return value was incorrectly modified to "nil".

  • Fixes the problem where RocketMQ instrumentation did not use API CallContext, resulting in compilation errors.

  • Fixes the incorrect instrumentation issue in Iris.

  • Supports Go Mod Vendor.

  • Supports printing HTTP headers and bodies.

  • Updates Kitex version support to 0.12.1, Fiber version support to 2.52.6, and Hertz version support to 0.9.4.

  • Improves agent performance by 10%.

1.4.2

January 6, 2025

  • Fixes the issue of incorrect instrumentation in the Go Micro client.

  • Fixes the problem where Logrus instrumentation does not take effect.

  • Adds debug logging for OpenTelemetry SDK instrumentation.

  • Fixes the issue where spans in gRPC streams do not end properly.

  • Changes the handling of Redis nil returns to not be treated as errors in Redis v9.

  • Fixes the issue where non-UTF-8 SQL statements cause span reporting failures.

  • Fixes the compilation failure issue when GOROOT and GOPATH are the same.

  • Updates Kratos version support to 2.8.3, gRPC version support to 1.69.2, GORM MySQL version support to 1.0.4, Gorm.io/Gorm version support to 1.20.12, and Redis version support to 8.10.0.

1.4.1

December 16, 2024

  • Adds debug logs to assist with problem localization.

  • Fixes the issue where ARMS Baggage was not being propagated correctly.

  • Adds specified Attributes for code hotspots, making the code diagnostics feature available for use.

  • Fixes the Panic issue caused by Go Race compilation.

  • Fixes the problem of incorrect span collection in Kitex.

1.4.0

December 10, 2024

  • Changes the compilation method to simply add ./instgo before running go build, simplifying the modification process.

  • Supports custom extensions.

  • Supports configuring trace propagation protocols.

  • Supports associating trace IDs with CPU profiling.

  • Updates fasthttp version support to 1.57.0, Kratos version support to 2.8.2, OpenTelemetry SDK version support to 1.32.0, Redis v9 version support to 9.7.0, and Restful version support to 3.12.1.

  • Supports OpenTelemetry SDK traceProvider ForceFlush.

  • Improves agent performance by 7%.

1.3.5

December 4, 2024

  • Fixes the issue where interface filtering was ineffective.

  • Updates the supported version of Kitex.

  • Fixes the problem of trace linking failure in Kitex after receiving gRPC requests.

1.3.4

November 25, 2024

  • Fixes the issue of compilation failure caused by version mismatches between GORM and MySQL.

  • Fixes the situation where OpenTelemetry SDK does not support shutdown.

  • Resolves the compilation failure caused by function name conflicts between ApsaraMQ for RocketMQ and AMQP.

  • Changes the default setting for OpenTelemetry SDK, Mux, Restful, Micro, and Echo frameworks to be disabled by default.

  • Updates gRPC support to the latest version 1.68.0.

  • Updates fasthttp version support to 1.57.0, Kratos version support to 2.8.2, and OpenTelemetry SDK version support to 1.32.0.

1.3.3

November 17, 2024

  • Fixes the mismatch issue between HTTP Server statistics for 4xx errors and span records.

  • Fixes the incorrect propagation of sampling flags.

  • Fixes the issue where timezone settings prevent profiling data from being queried.

  • Fixes the HTTP and gRPC instrumentation issues in Kratos.

1.3.2

November 7, 2024

  • Reduces client span writes to Global Load Store (GSL), decreasing performance overhead.

  • Supports filtering for span names in OpenTelemetry SDK instrumentation.

  • Fixes the conflict issue between Redis v8 instrumentation and user instrumentation.

  • Fixes the issue where the log association switches do not take effect.

  • Supports New Root Span and SpanKind in OpenTelemetry SDK instrumentation.

  • Fixes the inaccurate CPU consumption reporting in Elastic Compute Service (ECS) instance monitoring.

  • Fixes the non-UTF-8 serialization error in Redis v8.

  • Fixes the issue of recording errors when Redis v8 keys do not exist.

  • Increases gRPC version support to 1.67.1.

  • Enables CPU profiling and memory profiling by default.

  • Modifies profiling data reporting to use timestamps as names to distinguish reports from different time zones.

1.3.1

October 25, 2024

  • Fixes the issue of context propagation failure in OpenTelemetry SDK instrumentation.

  • Fixes the issue of trace propagation failure in Java EagleEye.

  • Fixes the issue of compilation failure on Windows.

  • Fixes the issue where System metrics cannot be retrieved, causing metrics not to be reported.

  • Fixes the issue where the go.sum file is not restored after compilation.

  • Fixes the incorrect exception recording issue in Redis v8.

  • Changes the "Kind" of intermediate spans to "internal".

  • Modifies the length of exception records by default, increasing it by 2,000 characters.

1.3.0

October 15, 2024

  • Modifies Echo version support range to 4.0.0 - 4.12.0.

  • Supports Iris support 12.0.0 - 12.2.12.

  • Supports Fiber 2.43.0 - 2.52.6.

  • Supports Kafka.

  • Supports memory profiling.

  • Supports full sampling for error interfaces and slow interfaces.

  • Supports viewing SQL-related parameters.

  • Supports configuring length for exception event reporting.

  • Supports exposing Redis command parameters.

  • Adds agent startup log printing and configuration to not collect system metrics on Mac operating systems.

  • Supports Redis Go.

  • Supports compilation with Vendor.

  • Supports instrumentation for logs from the Go native log package and slog library.

  • Supports Function Compute SDK for Go.

  • Updates gRPC version support to 1.67.0.

  • Updates fasthttp version support to 1.56.0.

  • Updates Kratos version support to 2.8.0.

  • Adds plug-in switches.

  • Adds the Call Chain Distribution, Upstream and downstream analysis, and Convergence setting pages.

1.2.6

September 20, 2024

  • Increases supported Echo version up to 4.0.0.

  • Fixes the function name conflict issue between ApsaraMQ for RocketMQ and Kafka.

  • Fixes the missing out ids issue in HTTP Client.

  • Fixes the probabilistic undefined issue in Redis v8 functions.

  • Optimizes log output.

  • Fixes compilation errors caused by including OpenTelemetry rules in imports.

  • Supports the segmentio/kafka-go component.

  • Supports exposing database SQL parameters.

  • Fixes the issue where spanFromContext in OpenTelemetry SDK does not take effect.

  • Fixes the Gin middleware panic issue.

  • Supports Fiber and Iris.

  • Fixes the issue of broken traces caused by duplicate instrumentation in gRPC Client.

1.2.0

August 30, 2024

  • Supports Zerolog, Hertz, and ApsaraMQ for RocketMQ plug-ins.

  • Adds interface filtering configuration for data collection.

  • Fixes gRPC Client instrumentation issues and supports NewClient instrumentation.

  • Supports instrumentation in the OpenTracing framework.

  • Adds configuration limits for excessively long SQL statements and adds slow SQL timeout configurations.

  • Fixes the issue where configuration tags do not take effect on metrics.

  • Refactors database, Redis, Kratos, Dubbo, Mux, Net/HTTP, gRPC, and GORM code according to the open-source version. Open source repository: https://github.com/alibaba/opentelemetry-go-auto-instrumentation.

  • Supports configuring HTTP status code whitelists and setting slow request timeout durations.

  • Fixes the issue where the fasthttp handler method is not supported.

1.1.0

July 30, 2024

  • Supports Elasticsearch, Logrus, Zap, Kafka, PostgreSQL, and Thrift.

  • Supports CPU profiling.

  • Improves agent performance by 20%.

  • Increases support for Gin, Go Micro, and fasthttp versions.

  • Supports quantiles.

  • Introduces log analysis and log association capabilities.

  • Fixes the issue where "instgo clean" fails to clear the environment.

1.0.7

July 22, 2024

  • Fixes the panic issue caused by not adding ARMS environment variables.

1.0.6

July 20, 2024

  • Supports more Gin, gRPC, and GORM versions.

1.0.5

July 19, 2024

  • Fixes the compilation failure related to using the go work command in the code directory.

1.0.4

July 17, 2024

  • Supports more GORM versions.

1.0.3

July 12, 2024

  • Fixes the SQL convergence issue.

1.0.2

July 8, 2024

  • Supports gRPC 1.51.0.

1.0.1

July 3, 2024

  • Resolves the Go path conflict issue.

1.0.0

June 27, 2024

  • Supports non-intrusive integration of Go applications with Application Monitoring, providing capabilities such as tracing, performance monitoring, and intelligent alerting.

Python agent

Version

Release date

Release notes

1.6.1

July 28, 2025

Fixed issues

  • Fixed the issue where the agent unexpectedly reported self-monitoring logs over the Internet when liveness probes failed.

1.6.0

July 22, 2025

New features

Fixed issues

  • Fixed the issue where the time consumption statistics of the Flask plugin were inaccurate.

  • Fixed the issue where the exception count of the Flask plugin was inaccurate.

  • Fixed the issue where the LLM application type failed to be detected.

  • Fixed the issue where incorrect exception information was displayed when an exception occurred during an OpenAI plugin call.

  • Fixed the issue where the LangChain plugin occasionally miscalculated tokens.

1.5.1

July 9, 2025

New features

Fixed issues

  • Fixed the issue where the call chain of Dify plugin Chat/Completion applications was broken.

  • Fixed the incompatibility error that occurred when the Dify plugin started a service using gevent.

  • Fixed the issue where upstream and downstream call chains failed to be associated in some scenarios.

  • Fixed the package conflict issue with other third-party dependencies of Alibaba Cloud in some scenarios.

1.4.0

June 23, 2025

New features

Fixed issues

  • Removed grpc-exporter-related dependencies to reduce the possibility of dependency conflicts.

  • Fixed the issue where user calls failed in DashScope streaming scenarios.

  • Fixed the attributes warning caused by None. By default, Nacos error logs are not printed to standard output.

  • Fixed the issue where the spanKind task was lost in Dify workflows.

  • Fixed the issue of duplicate input and output in the Dify plugin.

  • Fixed the issue where the response was not as expected during asynchronous OpenAI calls.

1.3.1

May 23, 2025

Fixed issues

  • Fixed the issue where metadata such as the service name was occasionally not obtained when the agent reported data in some scenarios.

  • Fixed the issue where the version number of the Python agent was displayed incorrectly.

1.3.0

April 23, 2025

New features

Fixed issues

  • Limited the supported versions of the Dify framework to prevent call errors when users use a Dify framework version that is not supported by the agent.

1.2.0

March 13, 2025

New features

  • Added the vLLM plugin.

  • Added LLM metrics to the LangChain plugin.

  • Added support for Python 3.12.

Fixed issues

  • Resolved the compatibility issue with the OpenTelemetry API.

  • Fixed the issue where the LangChain plugin changed the log level.

  • Fixed the issue where prompt information was not collected by the LangChain plugin.

1.1.0

January 6, 2025

  • Added support for the Dify plugin.

  • Added support for the HTTPX plugin.

  • Added support for associating business logs of applications with trace IDs. For more information, see Associate the business logs of a Python application with a trace ID.

  • The OpenAI plugin supports LLM application metrics.

  • The LlamaIndex plugin supports LLM application metrics.

  • The LlamaIndex plugin supports the time to first packet (TTFP) metric.

  • Fixed the issue of incorrect labels for Flask metrics.

  • Fixed the issue of duplicate trace IDs and span IDs in scenarios where the Random operator is set.

  • Fixed the compatibility issue between the agent and the OpenTelemetry package.

1.0.0

September 24, 2024

  • Added support for non-intrusively registering Python applications with ARMS Application Monitoring to provide features such as Tracing Analysis, performance monitoring, and smart Alerting.