ccfos/nightingale

Maintainer? Show your league in your README

Card: your league's emblem, from Copper to Legendary

[![bestofgithub](https://bestofgithub.dev/badge/ccfos/nightingale.svg?style=card)](https://bestofgithub.dev/repo/ccfos/nightingale)

Flat: fits beside your other badges

[![bestofgithub](https://bestofgithub.dev/badge/ccfos/nightingale.svg)](https://bestofgithub.dev/repo/ccfos/nightingale)

Loading README…

Capability	What you can do
Alerting across data sources	Use PromQL, log queries, or SQL to define conditions. Apply a rule to multiple instances of the same data source type.
Team ownership	Group rules and dashboards by business group, assign team permissions, and connect OIDC, OAuth2, LDAP, or CAS for sign-in.
Event processing and routing	Mute notifications, subscribe to alerts, enrich or rewrite labels, and route events through conditional pipelines.
Alert execution records	Review evaluation queries and results, active and historical events, and notification delivery records.
Reusable integrations	Start with bundled collector configurations, alert rules, and dashboards. Review queries and thresholds for your environment before enabling them.
Distributed evaluation	Distribute rules across alerting engines and use `n9e-edge` to evaluate alerts close to remote data sources.

Option	Start here
Local evaluation with Docker Compose	Included Compose stack
Linux binaries for amd64 and arm64	Release downloads and configuration reference
Kubernetes	Helm chart and installation instructions

Why Nightingale?