Agent Version Information
Last updated:2026-01-06 11:21:20
This document presents the version information of Tencent Cloud's self-developed APM agent and provides a download address. For details on agents or SDKs provided by the open-source community, including OpenTelemetry, Skywalking, Jaeger, etc., see the corresponding open-source community documentation.
Tencent Cloud OpenTelemetry Java Agent Enhanced Edition
Tencent Cloud OpenTelemetry Java Agent Enhanced Edition is based on the openTelemetry-java-instrumentation from the open-source community and developed further under Apache License 2.0. It includes a reference to the OpenTelemetry License within the agent packet. Building on the open-source agent, the Tencent Cloud OpenTelemetry Java Agent Enhanced Edition has made significant improvements in areas such as Event Tracking density, advanced diagnosis, performance protection, and enterprise-level capabilities. In addition, the Tencent Cloud OpenTelemetry Java Agent Enhanced Edition also adheres to the OpenTelemetry protocol standards. When the automatic Event Tracking does not meet user scenarios, you can see OpenTelemetry official documentation for customizing business Event Tracking.
Version | Release Note | Release Date | VPC Private Network Download Address | |
| Support the inheritContext parameter of the @WithSpan annotation to start a new trace. Support obtaining parameters of PreparedStatement and saving them in Span attributes. Fix GraphQL component tracking issues. | 2025-12-31 | Hong Kong (China) |
|
| | | Singapore |
|
2.11-20251107 | Bug Fix: Fix the issue where the callback method of Redisson tracking RPromise does not take effect after being canceled. Fix Kafka multi-Broker scenarios. | 2025-11-07 | - | - |
2.11-20250930 | New feature: Support viewing circuit breaker events for probes in the console. Support Undertow thread pool instrumentation. Bug Fix: Fix memory leak problem caused by automatic event tracking for HttpUrlConnection. Optimize computation logic for CPU usage in container scenario. Fix data failure issue in Hikari connection pool under special scenario. | 2025-09-30 | - | - |
2.11-20250825 | New feature Supports dynamically setting the probe fuse threshold. Optimize performance analysis statistical result status (various collection failure reasons). Optimize thread pooling/connection pool metric collection (naming specification and collection count). Support setting the call source field. Unify the associated group of thread pools for internal use by probes. Bug Fix: Fix null pointer exceptions and CPU spikes in the template engine detection feature in some scenarios. Fix memory leak problem with statement objects in some scenarios. | 2025-8-25 | - | - |
2.11-20250704 | Application security feature support includes analysis of various types of attack behavior, such as template engine injection detection, JNDI injection detection, and JNI injection detection. For Druid Connection Pool, add new targeting for the getConnection method. Enable Mybatis related component tracing by default. | 2025-7-4 | - | - |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
2.11-20250509 | Support Arthas. Support remote command attack detection and Java Webshell attack detection. Support JVM buffer metric reporting. Fix CPU performance issues | 2025-5-9 | - | - |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
2.3-20250228 | Fix the problem where probes in some sub-environments cannot obtain the instance name. JVM runtime metrics cover more GC recyclers and memory areas. | 2025-2-28 | - | - |
2.3-20250131 | Support performance analysis for the new version. Support OkHttp thread pool analysis capability, and connection pool analysis capability for frameworks such as Hikari and Redisson. | 2025-01-31 | - | - |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
2.3-20241231 | Support method stack analysis feature. Optimize probe performance in high-load scenarios. | 2024-12-31 | - | - |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
2.3-20241130 | Support application security related features. Support thread analysis feature. Support JVM ZGC metric reporting. | 2024-11-30 | - | - |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
2.3-20241031 | Support through Skywalking Cross Process Propagation Headers Protocol to implement Cross-application link information transmission. Support reporting custom metrics through OpenTelemetry API and output to the associated Prometheus instance. Support customizable thresholds related to application retention mechanisms. | 2024-10-31 | - | - |
2.3-20240930 | Newly-added JVM metric reporting: code cache, compressed class space. Optimize instrumentation feature richness for DB calls, with automatic reporting of database type, database address, and additional information. | 2024-09-30 | - | - |
2.3-20240831 | Support multiple probe configurations, which can be managed and operated through the console and take effect immediately. Add new ons-client automatic event tracking. Address potential performance issues when using the Fastjson library. | 2024-08-31 | - | - |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
2.3-20240730 | Support Java 21. Add new XXL-JOB 1.9.2+ automatic event reporting. Support automatic event reporting for Spring Service annotation methods. | 2024-7-30 | - | - |
2.1-20240701 | Support custom event tracking enhancement through OpenTelemetry API. Add new automatic event tracking support for a series of components and frameworks, including Spring Cloud Gateway 2.0+ and Pulsar 2.8+. | 2024-7-1 | - | - |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
1.16-20240328 | Optimize probe stability in high-load scenarios. | 2024-3-28 | - | - |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
1.16-20240305 | Support thread pool and connection pool metric reporting. Analyze the root cause of high CPU/memory load through flame graphs. | 2024-3-5 | - | - |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
Agent Support Cycle
To continuously enhance the product capabilities and stability of Tencent Cloud OpenTelemetry Java Agent Enhanced Edition, support new versions of open-source components, and promptly fix agent defects and security vulnerabilities, APM will continuously iterate the agent, regularly releasing new versions. It is recommended to follow the release cadence and update the agent version timely.
Each officially released Tencent Cloud OpenTelemetry Java Agent Enhanced Edition, from the release date, has a fixed support period of 6 months. Starting from the 4th month, APM will notify you in the console that the agent is nearing expiration. From the 6th month, APM will notify you in the console that the agent has expired. After the agent expires, it will not affect the use of APM; if you need technical support for the agent, it is recommended to upgrade the agent version first. For upgrading, see Upgrading Agent Version.
Tencent Cloud OpenTelemetry Go Probe
Tencent Cloud OpenTelemetry-Go Probe is developed based on the community opentelemetry-go-auto-instrumentation project. With this solution, Go applications can access APM without modifying the business code. It provides automatic event tracking support for commonly used Go dependency libraries and frameworks such as Gin, GORM, and gRPC. For other dependency libraries and frameworks that support automatic event tracking, see the complete list.
Edition | Release Note | Release Date | Download Address |
1.0.1 | Support performance analysis Support collection of CPU and memory usage | 2025-10-14 | |
0.10.2 | Allow offline builds with -mod=vendor New binding via go:linkname Support kafka-go | 2025-7-3 |
Other Agents
Besides Tencent Cloud OpenTelemetry Java Agent Enhanced Edition, other agents are provided by the open-source community, including the OpenTelemetry community, and Skywalking community. See the connect guide for agent installation.
For applications deployed on TKE, the Tencent Cloud Observability team provides an Operator scheme: tencent-opentelemetry-operator. Built upon the community opentelemetry-operator, it enables agent auto-injection, facilitating applications to connect APM quickly. Currently, tencent-opentelemetry-operator supports the following agent versions:
Language | Agent Version | Release Notes | Release Date |
Python | 0.45b0 (Latest Version) | 2024-6-4 | |
| 0.41b0 | 2023-10-13 | |
Node.js | 0.51.0 (Latest Version) | 2024-6-24 | |
| 0.44.0 | 2023-10-25 | |
.Net | 1.6.0 (Latest Version) | 2024-4-29 | |
| 1.2.0 | 2024-1-18 | |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback