Abstract

jaque runs soft and hard states, acknowledgements, downtimes, dependencies and escalations on an event-sourced core, shipped as one static binary. The semantics match what a Nagios operator already knows. Plugins written for the Nagios exec protocol run unmodified. A Nagios config compiles to native CUE, with a report of what mapped and what did not. Anything that speaks Livestatus keeps working. Every state transition is a pure function folded over an append-only event log, so the current state is a projection, and replaying the log reproduces it.

Status of This Document

These pages describe software offered for production use. Packages and archives are public (see Install). The status page states what is built, what is implemented but unverified, and what does not exist, with the evidence for each mark. Read it before believing anything below. Each page carries its own Status: line where some part of it is unverified or absent.

Table of Contents

1. Introduction: install it from the package repository or the archive, write a three-line config, watch it decide; then point the importer at a Nagios tree.
2. The model: the pipeline from scheduler to log to projections, the state machine that decides when to page, why every fact is an event, and why the config is CUE.
3. Checks: native checks, Nagios exec-protocol plugins, WASM checks and command checks, all behind one Runner interface.
4. Configuration: CUE in practice, labels and views, SIGHUP hot reload, and the schema reference.
5. Notifications: contacts, policies, escalation ladders, time windows and the adapters that deliver.
6. Ingest: results that arrive instead of being fetched: passive checks, the FIFO and API, SNMP traps.
7. Running it: one binary, the topologies the -target roles produce, cluster coordination, Kubernetes, Docker, security and operations; choose your deployment routes straight to a guided walkthrough.
8. Observing it: the dashboard, the engine's own metrics, perfdata sinks and the event archive.
9. Nagios compatibility: exec plugins, FIFO external commands and Livestatus, supported with no sunset date; the importer that compiles the rest.
10. Reference: CLI flags, the event log schema, the command and query service, and the status JSON.
11. Project: what is shipped, unverified or unbuilt; the roadmap, the design decisions, the changelog, and the terms and privacy pages.

Chapters 1, 2, 9 and 11 are narrative: each page states a rule, the reason for it, and what breaks when it is ignored. Chapter 10 is reference: tables, no adjectives, every key documented once.