Azul Intelligence Cloud Agent Release Notes

API v2 is enabled by default. The Agent now uses the v2 protocol by default. Deduplication is handled within the Forwarder. You don’t need to configure this on the Agent side.

Memory safeguards are disabled by default. The protectAppResources option (previously memorySafeguards) is now false by default. To re-enable, add protectAppResources=true to the Agent arguments. See CRS Arguments for more information.

Fixed a deadlock during initialization of the Agent when running alongside other Java agents (e.g., Datadog) that load classes concurrently at startup.

Fixed ClassCircularityError in reference handling.

Fixed an AppEnv serialization issue.

The Agent no longer sends stripped jar-loaded events when artifact upload has failed.

Updated the ASM library to version 9.8 (adds JDK 25+ support).

Jar load reporting now supports .war, .ear, and .sar file extensions.

Added reporting of jars from SystemClassLoader.

General bug fixes and QOL improvements.

Logs generated by the agent, are now forwarded to Azul Intelligence Cloud by default. This can be disabled with the option sendCRSLogs=false. Only ERROR logs are sent by default. See CRS Arguments for more information.

A new CRS argument memorySafeguards=<true/false> is available to let the agent recognizes that it competes for memory with the application. When this happens, it will proactively free its memory and terminate itself. This feature is enabled by default. See CRS Arguments for more information.

To reduce the amount of data sent between JVMs, the Forwarder, and Azul Intelligence Cloud, the JVMs no longer send a continuous "heartbeat", but only the data needed for the reports in Intelligence Cloud.

Therefore, for the from and to filters, you must consider when a JVM sent data to Intelligence Cloud, which may differ from how long the JVM has been running.

See API Request Parameters > Filter Range.

General bug fixes and QOL improvements.

General bug fixes and QOL improvements.

General bug fixes and improvements.

With this release, the Agent can now also be configured with the CRS option notifyFirstCall to report the first method invocations. See Diagnostic Configuration Options.

The default temporary file system space is increased from 2MB up to 20MB for maxJarFileCache, see Diagnostic Configuration Options. In this space, jar files are cached for analysis. Nested jars with a bigger size than this limit will not be reported to the backend. Make sure to update this value if you have such bigger nested jars.