Overview

Nobody rips out a Nagios estate in a weekend. jaque’s compatibility story is built for the estate you already have: your plugins keep running, your existing consoles keep reading, your configs get compiled rather than hand-rewritten.

The pitch

You should be able to point jaque at your existing Nagios plugins and config, get the same operational picture out of your existing tools (Thruk, NagVis), and only then decide — on your own schedule — whether to adopt jaque’s own dashboard, CUE config, or notification model. None of that is required to start.

Four legs of compatibility

• Exec plugins — any script speaking the exit-code protocol runs unmodified, forever.
• FIFO external commands — the same wire format existing tooling already writes to.
• Livestatus — the read protocol Thruk, NagVis, and Checkmk already speak, so they can point at jaque without a config change.
• Importer — compiles a Nagios config tree to native CUE, with a report on exactly what translated and what didn’t.

Each of these carries forward not just the wire format but the semantics behind it — soft/hard states, acks, downtimes — the actual behavior Nagios-class tooling expects, not just a compatible-looking surface.

What this is not

jaque will never execute a legacy Nagios config at runtime. Every compatibility surface above is either a permanent protocol adapter (exec plugins, FIFO, Livestatus) or a one-time compiler pass (the importer). There is no “legacy mode” that reads nagios.cfg directly and runs it; the config you run is always jaque’s own CUE, whether you wrote it by hand or an importer emitted it.