Visit Azul.com Support

Azul Intelligence Cloud Agent Release Notes

The Intelligence Cloud Agent is the prefered way to connect your Java Virtual Machine (JVM) with the Forwarder to send all the required data to your Intelligence Cloud instance. More information is available in Using the Azul Intelligence Cloud Agent.

Azul Intelligence Cloud Agent 1.3.0

Release date: November 5, 2026

The Azul Intelligence Cloud Agent 1.3.0, in combination with the Forwarder 2.1.0, introduces Azul Intelligence On-Premises. It also adds Deep Identification, Focused Code Inventory, and a self-diagnostic tool.

Note
This release is designed to work with Forwarder 2.1.0.

What’s new

  • Deep Identification (Azul Intelligence On-Premises): The Agent looks past common launchers and application servers, and reports what identifies the application that they run. The inventory of Azul Intelligence On-Premises then shows a meaningful application name instead of a generic one like org.springframework.boot.loader.launch.JarLauncher. Supported are Spring Boot, Apache Tomcat, plain Java applications (started with a main class or with java -jar), and applications started through the Java Service Wrapper (Tanuki). Deep Identification is enabled by default, and only applies to new observations. To turn it off, set disableDeepIdentification=true. See CRS Arguments for more information.

    The Agent sends only the application title, start class, main class and Spring Boot version from the manifest, the file name of the application archive, and the recognized launch type. It doesn’t send the command line, system properties, or environment variables. Azul Intelligence Cloud doesn’t use this data. If you don’t want the Agent to send it to Azul Intelligence Cloud, set disableDeepIdentification=true.

  • Focused Code Inventory (Azul Intelligence Cloud): Code Inventory can now be scoped to your own code. The policies that you configure in Azul Intelligence Cloud tell the Agent which packages to report. The Agent skips third-party libraries, frameworks and generated classes before sending anything. This reduces network traffic and processing. No Agent configuration is needed, but the policies match the AppEnv tag of the JVM. By default, a JVM collects nothing until a policy allows it, so Azul Intelligence Cloud creates a default policy that you can edit. Agents older than 1.3.0 ignore the policies. See Focused Code Inventory.

  • Artifact compression: When the Agent reports a JAR with full details, large reports (over 512 KB) are uploaded as separate artifacts. The Agent now compresses these reports with gzip before the upload, which reduced the upload size by about two thirds in tests (660 KB to 220 KB). The compression runs in the background upload thread of the Agent, not in the threads of your application. It is enabled by default. To upload the reports uncompressed as before, set compressArtifacts=false. See CRS Arguments for more information.

  • Self-diagnostic tool: The Agent JAR can check your environment before you attach it to an application. Run java -jar <agent jar> diagnose with the same options that you use for -javaagent. The tool checks the Java version and the JDK prerequisites, the Agent options, tags and feature flags, and the connection to the Forwarder. It tells you what to fix, and it doesn’t send any data or change anything.

  • Plain HTTP connection to the Forwarder: The Agent can connect to the Forwarder over plain HTTP, in addition to HTTPS. This is intended mainly for Azul Intelligence On-Premises installations, where no Azul-issued certificate is available, and for environments where TLS is terminated elsewhere. Enable it explicitly with noSsl=true, and allow plain HTTP on the Forwarder too. See CRS Arguments for more information.

    Warning
    With plain HTTP, the authentication token of the Agent and all observations travel unencrypted. Use it only on networks you trust. For production, use HTTPS with a certificate from your own certificate authority.
  • Software Bill of Materials (SBOM): Each Agent release now comes with a SBOM in CycloneDX format, which lists the third-party components that the Agent contains. It is published as a separate file, crs-a-agent-<version>-cyclonedx.json, next to the Agent JAR.

  • macOS support: The Agent collects macOS-specific system attributes.

Behavior changes

  • JDK system classes are no longer reported: Classes from the bootstrap class loader, and classes with the prefixes java/, jdk/, sun/ and com/sun/, are filtered before any transformer runs. About 65 classes from JDK system modules (for example jdk.crypto.ec and sun.security.ec) no longer appear in class load reports. These classes don’t contribute to code inventory analysis and were inconsistent across JDK versions. Application classes are not affected.

  • Focused Code Inventory limits what the Agent reports: Earlier Agents report everything. Agent 1.3.0 reports only the packages that your Focused Code Inventory policies allow. Review your policies before you upgrade.

Bug fixes

  • Fixed a deadlock during the initialization of the Agent on certain class loading patterns.

  • Fixed a potential ClassCircularityError when the class transformer of the Agent was invoked reentrantly.

  • Reduced the noisy log message during the shutdown of the Agent from error to trace level.

Improvements

  • Memory safeguard reliability: Hardened the shutdown sequence of the memory safeguard to prevent a rare race condition that could make an Agent worker thread consume excessive CPU after the safeguard was triggered. The primary fix was shipped in Agent 1.2.0, this release adds extra protection.

  • Protocol versioning: The batch metadata now includes the protocol version fields specMajor and specMinor, which allows compatible changes to the protocol between the Agent and the Forwarder. No action is required.

Azul Intelligence Cloud Agent 1.2.0

Release date: May 19, 2026

The Azul Intelligence Cloud Agent 1.2.0, in combination with the Forwarder 2.0.0, introduces deduplication, which runs on your infrastructure before any data leaves your network. The Forwarder identifies duplicate events across JVMs within the same application environment and transmits only unique events to Azul Intelligence Cloud. You get complete, accurate data at a fraction of the transfer cost.

Note
This release is designed to work with Forwarder 2.0.0 for deduplication. Don’t use this version of the Agent in combination with Forwarder 1.x.

What’s new

  • 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.

Bug fixes

  • 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.

Improvements

  • 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.

Azul Intelligence Cloud Agent 1.1.61

Release date: December 2, 2025

What’s New

  • 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.

Azul Intelligence Cloud Agent 1.1.49

Release date: May 28, 2025

What’s New

  • General bug fixes and QOL improvements.

Azul Intelligence Cloud Agent 1.1.34

Release date: March 27, 2025

What’s New

  • General bug fixes and QOL improvements.

Azul Intelligence Cloud Agent 1.1.22

Release date: January 21, 2025

What’s New

  • 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.

Azul Intelligence Cloud Agent 1.1.0

Release date: September 30, 2024

What’s New

With this release, the usage of the Azul Intelligence Cloud Agent has been simplified, as it now comes as a single JAR. This removes the need of additional parameters to configure the accessor.

Azul Intelligence Cloud Agent 1.0.0

Release date: March 18, 2024

Initial release of the Azul Intelligence Cloud Agent, an optional component that enables Intelligence Cloud functionality with older versions of Azul, as well as non-Azul JVMs.

To learn more, check the Using the Azul Intelligence Cloud Agent documentation.