Yagra is an open-source NMS written in Rust. ICMP, SNMP v2c/v3, HTTP and API checks; distributed pollers; alerting that won’t flood your on-call. It ships as Docker containers and scales out by config, not rewrite.
Rust · Tokio · Axum · React · PostgreSQL · VictoriaMetrics · NATS
Active and passive monitoring, discovery, alerting, and traffic analysis — designed to stay honest and quiet at scale.
Core and pollers talk only through the bus, so pollers are stateless, horizontally scalable, and deployable at remote sites across NAT and firewalls. They poll outward and receive passive intake inward — syslog, traps and flow exports — and each kind of data lands in the store built for it.
Core never calls a poller directly, and receives no device traffic of its own: syslog, SNMP traps and flow exports all land on a poller at the edge — including remote-site pollers behind NAT — and reach core over the bus. Inbound webhooks are the one exception, arriving straight on the API. NATS is the broker itself, a backing service like the stores; Bus is the client crate compiled into core and into every poller, which is why it appears in both.
Every one of these appears in the diagram above. Core, Poller and the WebUI are the processes you deploy; the small boxes drawn inside them are the Rust crates each process is built from, and the tag repeats which process that is.
The MVP runs co-located in a few containers; the same build scales out to distributed pollers and highly available stores by configuration.
Pollers hold no per-target state, so the coordinator assigns nodes across live pollers by consistent hashing and reassigns on heartbeat loss. Standing one up at a remote site is done from the WebUI: one switch encrypts and authenticates the bus, and issuing that poller a token downloads everything the site needs as a single archive — unpack it and start it. Remote pollers dial out to a central bus and buffer results through a network partition — replaying metrics on reconnect, while alerts are never backfilled so a recovered link can’t flood you with stale events.
The WebUI is HTTPS out of the box — import your own certificate from the UI, with no restart. Monitoring credentials are envelope-encrypted (AES-256-GCM) with the key held outside the database. Single sign-on via OIDC — with guided setup for Microsoft Entra ID, Okta and Google Workspace that asks only for what each product needs — sign-in against LDAP or Active Directory, role-based access control, an immutable audit log, and per-poller-scoped bus credentials. The advanced distribution and HA features are opt-in — defaults stay conservative and backward-compatible.
Fetch the Compose file and start it. That pulls the published images and brings up core, a poller, the WebUI and the backing stores (PostgreSQL, Redis, NATS, VictoriaMetrics) — no repository checkout, nothing to compile.
https://localhosthttp://localhost:8080$ mkdir yagra && cd yagra
$ curl -fsSL -o docker-compose.deploy.yml \
https://github.com/horryworks/Yagra/releases/latest/download/docker-compose.deploy.yml
$ docker compose -f docker-compose.deploy.yml up -dFirst start prints a one-time admin password to the core logs:
docker compose -f docker-compose.deploy.yml logs corePublished images:
ghcr.io/horryworks/yagra-core
ghcr.io/horryworks/yagra-poller
ghcr.io/horryworks/yagra-webRead the source, run it yourself, and follow every release on GitHub. No sign-up, no telemetry wall. v0.3.0 restructured the backend for the people who do read it: the largest files were split along the lines their contents already followed, and each new boundary is held by a test that fails the build when something crosses it.
Open beta: bug reports and questions go to GitHub Issues, the only contact channel for the project — there is no contact e-mail address. Pull requests are not being accepted at this time.