Java
  • 15 Oct 2024
  • 1 Minute to read
  • PDF

Java

  • PDF

Article summary

1.1.13 — 24th September

Resolved issues

  • The 1.1.13 release resolves an issue with gzip bodies in HTTP clients.

  • The 1.1.13 release resolves an issue with metrics with high cardinality flooding logs.


1.1.12 — 10th July

Resolved issue

  • The 1.1.12 release resolves the verifyError on some Spring applications.


1.1.10 — 18th June

Traceable’s Java agent 1.1.10 has the following:

Updates

  • Servlet 5.0 — The 1.1.10 release adds support for Servlet 5.0.


1.1.9 — 11th June

Traceable’s Java agent 1.1.9 is deprecated.


1.1.8 — 22nd April

Traceable’s Java agent 1.1.8 has the following:

Updates

  • OTEL version The 1.1.8 release upgrades the OTEL version to 1.33.0.

  • HyperTrace version The 1.1.8 release upgrades the HyperTrace version to 1.3.12

  • Logging The 1.1.8 release makes the logging configuration consistent across config files, environment variables, and system properties. For logging configuration, see Configurations variables in the Java agent topic.

Resolved issues

  • Blocking The 1.1.8 release resolves an issue with blocking any body for frameworks using BufferedReader to read the request body.

  • Vert.x client—The 1.1.8 release resolves an issue with data capture on the Vert.x client when streaming data is present.

1.1.7 - 27th February

Traceable’s Java agent 1.1.7 has the following updates:

  • Status code and response message - The 1.1.7 release supports custom blocking status code and response message. For more information, see Configuration Variables in the Java topic.

  • File logging options - The 1.1.7 release provides new file logging options. For more information, see Configuration Variables in the Java topic.

  • Statistics in logs—The 1.1.7 release provides new options for printing metrics and statistics in log files. For more information, see Configuration Variables in the Java topic.


Was this article helpful?

What's Next