You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: Receive Alertmanager webhook notifications in Mosaic #77
Mosaic's existing Alertmanager connection pulls active alerts from /api/v2/alerts. Operators also need a push delivery option that follows Alertmanager's notification routing, grouping, silences, and inhibition. Searches of upstream pull requests and open issues found no existing Alertmanager webhook receiver proposal; the Teams webhook PRs handle a different protocol.
Proposed solution
Add an optional, default-off Helm-managed receiver for Alertmanager's standard v4 webhook payload. Use a dedicated inbound bearer-token Secret, retain the UI machine token only inside the adapter, and convert grouped notifications into the existing Mosaic alert API. Use fingerprint-based IDs for retry upserts and remove resolved alerts from the UI list. Provide an internal Service and optional TLS ingress exposing only the receiver path, plus configuration, administrator responsibilities, and delivery tests.
This proposal covers alert ingestion. The existing browser-triggered Auto investigate path, a future unattended investigation worker, and Teams notification delivery are separate concerns. The UI's process-local store is also an explicit deployment limitation rather than a durable incident queue.
Activity