Help Center > > Service Overview> Change History

Change History

Updated at: Dec 28, 2021 GMT+08:00

Pinpoint Description

Table 1 Pinpoint description

Version

Released On

Description

1.0.47

2021-5-22

  1. Supported Kafka clients 2.0.x–2.8.x.
  2. Supported mariadb-java-client 1.2.x–2.4.x.
  3. Fixed known Undertow tracing issues.

1.0.43

2021-2-2

  1. Supported Cloud Service Engine (CSE) 2.0.
  2. Fixed known issues.

1.0.39

2020-11-23

  1. Optimized the transaction matching mechanism.
  2. Supported monitoring for direct buffer memory.

1.0.38

2020-11-09

Optimized the transaction self-learning capability.

1.0.36

2020-10-10

  1. Optimized ServiceComb tracing.
  2. Optimized JVM thread monitoring.

1.0.32

2020-8-27

  1. Supported Tomcat monitoring.
  2. Optimized the gRPC plug-in.

1.0.29

2020-05-09

Supported the Hystrix asynchronous mode of Spring Cloud OpenFeign.

1.0.28

2020-02-12

Fixed the Redis Lettuce bug (that is, memory leakage may occur).

1.0.27

2019-11-30

  1. Supported the MySQL mysql-connector-java-8.x.x client.
  2. Supported the Redis Lettuce client.
  3. Supported the new Jetty version.
  4. Fixed the Netty bug (that is, memory leakage may occur).
  5. Optimized probe resource usage.

1.0.14 (latest CCE version)

2019-10-30

Supported Apache Dubbo 2.7.1.

1.0.4

CCE

2019-05-06

  1. Supported gRPC 1.11.x–1.14.x.
  2. Supported Thrift 0.11.

0.1.36

CCE

2019-03-15

  1. Supported ServiceComb 2.3.25–2.3.52.
  2. Supported Netty 4.1.22.
  3. Solved the JDK HTTP tracing interruption.
  4. Supported Docker application access for non-CCE users.

0.1.25

CCE

2018-12-24

  1. Supported JVM metric monitoring.
  2. Supported configuration of return codes and exceptions to be ignored.
  3. Added the http.url attribute to the tracing of the JDK HTTP client.
  4. Supported parameter collection for method tracing.

Feature Description

Table 2 Feature description

Released On

Description

2019-06-11

Supported transaction grouping and rule customization.

2019-06-04

Supported installation, upgrade, and uninstall of the ICAgent for non-HUAWEI CLOUD hosts.

2019-05-22

1. Connected Docker applications to APM.

2. Connected Deployment applications to APM.

2019-04-18

Obtained an Access Key ID/Secret Access Key (AK/SK) by creating an Identity and Access Management (IAM) agency.

2019-03-15

Supported customization of threshold rules and statistics for JVM monitoring.

2019-03-06

Optimized service and instance metrics, and displayed topology details to enhance full-link topology functions.

2018-12-26

  1. Monitoring of JVM memory and thread: Displays metrics about the JVM heap memory, JVM non-heap memory, and thread to quickly detect exceptions such as memory leakage and thread suspension.
  2. Exceptions whitelist: Set return codes and exceptions to be ignored.

2018-07-20

Supported both pay-per-use and package billing modes. For more information, see Application Performance Management Pricing Details.

2018-06-11

Launched Application Performance Management (APM) at the HUAWEI CLOUD international website.

ICAgent Description

Table 3 ICAgent description

ICAgent Version

Description

5.12.43

Resolved the problem that the ICAgent occasionally restarts during collection of container logs.

5.12.42

Resolved the problem that the number of network connections in close_wait state is sometimes too large during collection of rsyslog logs.

5.12.36

  • Supported display of O&M information by application or component in CCE scenario.
  • Optimized the calculation formula of node CPU usage.

5.12.35

Fixed log truncation in some scenarios.

5.12.32

Solved the problem that the ICAgent may restart during log collection.

5.12.29

Disabled metric collection for D310 chips.

5.12.27

Optimized application discovery rules.

5.12.26

Supported collection of text file logs in a specified path. There are no restrictions on file suffixes.

5.12.23

Added the file system usage metric for containers.

5.12.22

Supported log paths containing wildcards for recursive traversal.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel