Visit Azul.com Support

Ic On Premises 1.2.0

Table of Contents
Need help?
Schedule a consultation with an Azul performance expert.
Contact Us

Azul Intelligence On-Premises 1.2.0

Release date: November 18, 2026

Azul Intelligence On-Premises 1.2.0 makes new JVMs appear within about 15 minutes, adds an MCP endpoint for assistants and agents, and counts vendors by installation on the Trends screen.

You can upgrade in place from 1.1.x, over the same data directories, as described on Upgrading Your Installation. No database migration runs and no setting is required, because the new settings have defaults. Restart your Forwarders after the upgrade to apply the five-minute delivery age at once.

Upgrade Impact

  • MCP on the application port: A reverse proxy in front of your installation only has to pass /api/public/v1/mcp. A request with a browser Origin is refused unless LJVMI_PUBLIC_API_MCP_ALLOWED_ORIGINS lists it.

  • Vendor Mix figures rise: Where a machine holds several JDKs, each installation counts under its own vendor. An integration that reads GET /api/public/v1/inventory/trends sees no change.

What’s New

  • Seal age for Forwarders: Your installation tells each Forwarder when to seal a delivery, with FORWARDER_SEAL_AFTER (five minutes by default). A new JVM appears within about 15 minutes instead of after up to the 10-hour limit of the Forwarder. See Ingestion.

  • MCP endpoint: Assistants and agents connect at /api/public/v1/mcp with the same API tokens and limits as the public API. Settings > MCP shows how to connect Claude Code, Codex or curl. See Connecting an MCP Client.

  • Trends by installation: GET /api/public/v1/inventory/trends/installations returns trends counted by installation, as the Trends screen shows them. GET /api/public/v1/inventory/trends keeps counting machines.

Behavior Changes

  • Vendor Mix counts installations: Trends > Vendor Mix Over Time and the vendor counts on Fleet at a glance count installations, each under its own vendor. Fleet size and new machines found still count machines.

  • Fewer Agent event types stored: Ingestion stores only VM_CREATE, VM_PATCH and VM_APP_LOADED. Other lines are skipped and do not count against the quota.

  • About page caption: The diagram captions AMT scans as "JDKs on disk".