PRE-ALPHA

Abstract

jaque runs the semantics a Nagios operator already speaks -- soft and hard states, acknowledgements, downtimes, dependencies, escalations -- on an event-sourced core, shipped as one static binary. 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. You do not migrate to jaque; jaque moves into your house.

Status of This Document

These pages describe pre-alpha software. There is no public release and no public repository; the binary is handed directly to people granted access, and it is not yet ready to carry production monitoring. 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 -- run the binary, 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.
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 forever; 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 and the changelog.

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.