System Overview
Azul Intelligence On-Premises builds its JVM inventory from what your JVMs report. The Azul IC Agent reports the JVMs it is attached to, and AMT scans report the hosts that run no Agent. A Forwarder delivers both into your installation, which turns every delivery into inventory.
flowchart LR
subgraph yours["Your infrastructure"]
direction LR
agent["JVMs + Agent"]
amt["AMT scans"]
fwd["Forwarder"]
inbox[("Inbox (filesystem or S3)")]
subgraph app["Azul Intelligence On-Premises"]
direction LR
subgraph ingest["Ingestion pass"]
direction TB
s1["Discover sealed files"] --> s2["Normalize"] --> s3["One DB transaction"] --> s4["Ledger and quota"] --> s5["Acknowledge"]
end
store[("Event store (embedded DB)")]
api["Application API"]
ui["Web UI"]
pub["Public API (API tokens)"]
end
agent --> fwd
amt --> fwd
fwd --> inbox
inbox --> ingest
ingest --> store
store --> api
api --> ui
api --> pub
end
Components
- JVMs + Agent
-
The Azul IC Agent attached to a JVM reports what runs on your hosts. See Installing the Agent.
- AMT scans
-
Scans of hosts on which you don’t attach an Agent.
- Forwarder
-
Receives the Agent events and the AMT results, and delivers both to your installation as sealed files. See Installing the Forwarder.
- Inbox
-
Holds the files of each Forwarder, on a filesystem or in S3.
- Ingestion pass
-
Takes each delivery through five stages. It discovers the sealed files, normalizes them, writes them in one database transaction, updates the ledger and quota, and acknowledges the delivery.
- Event store
-
The embedded database that keeps the history as events. The fleet view is derived from it.
- Application API
-
Serves the data of the event store to the web interface and the public API.
- Web UI
-
The web interface of your installation. See The Web Interface.
- Public API
-
The integration API, which you call with API tokens. See The Integration API.