Visit Azul.com Support

Forwarder 2.0.0

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

Forwarder 2.0.0

Release date: May 19, 2026

Running hundreds or thousands of JVMs generates a large volume of events. Sending every event to Azul Intelligence Cloud is expensive in terms of network traffic, yet missing events means incomplete data and gaps in your analysis.

Forwarder 2.0.0 solves both problems at once. It 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 version of the Forwarder must be used in combination with the Azul Intelligence Cloud Agent 1.2.0 to be effective. For more information, see Agent 1.2.0 Release Notes.

What’s New

Event Deduplication: The forwarder now automatically filters duplicate events before forwarding them to Azul Intelligence Cloud. When multiple JVMs report the same classes, JARs, or methods, the forwarder detects duplicates and sends only unique events. This typically reduces network traffic between the forwarder and Intelligence Cloud by 85-95%.

Deduplication is enabled by default and requires no changes to your JVM agents.

Key Features

  • Two-layer caching: Fast in-memory cache for low-latency filtering, with an optional disk-based cache that preserves deduplication state across forwarder restarts.

  • Self-managing: The in-memory cache automatically manages memory under pressure. The disk-based cache auto-recovers from disk errors without manual intervention.

  • Deduplication monitoring: The health endpoint (/forwarder/health), status page, and Prometheus metrics now include deduplication statistics: saved bytes, dedup ratio, and cache health state.

  • Flexible deployment: Run with both caches (recommended), in-memory only (for stateless containers without disk), or as a passthrough proxy with deduplication disabled.

Updated Requirements

Component Previous (1.x) New (2.0) with deduplication

RAM

4 GB

8 GB

Disk

Not required

10 GB (SSD recommended)

CPU

1-2 cores

2 cores

-Xmx

1-2g

6g

Deduplication can be disabled (azul.deduplication.enabled=false) to retain the same resource requirements as Forwarder 1.x.

New Configuration Options

Setting (properties file) Description Default

azul.deduplication.enabled

Enable or disable deduplication

true

azul.deduplication.pipeline

ibf, lmdb (both caches) or ibf (in-memory only)

ibf, lmdb

azul.forwarder.fileCacheDirectory

Location for the disk-based cache

System temp dir

See Setting Up the Forwarder for more details.

Improvements

  • Prometheus metrics now include deduplication counters and ratios.

  • Health endpoint includes deduplication state in the overall health assessment.

  • Status page displays deduplication effectiveness (saved traffic, ratio).

Compatibility

  • Fully compatible with all existing Intelligence Cloud Agent versions

  • No agent-side configuration changes required

  • Upgrading from 1.x: update the forwarder JAR and increase memory/disk allocation per the updated requirements above