Ic Agent 1.3.0

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 rules that you configure in Azul Intelligence Cloud tell the Agent which classes and methods to report, so it skips third-party libraries, frameworks and generated classes before sending anything. This reduces network traffic and processing. No Agent configuration is needed. Without rules, the Agent reports as before.

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.

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.

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.

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.

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.