Alertmanager tells you something is wrong. It cannot tell you that a deploy went out four minutes earlier, because it has never heard of your deploys. Kollaber puts both on one timeline, which turns the usual question — what changed just before this fired? — into something you can read off the screen.
Point a webhook receiver at Kollaber with your environment UUID, and send the shared secret as a bearer token.
receivers:
- name: kollaber
webhook_configs:
- url: https://kollaber.io/webhooks/alertmanager?environment_id=<uuid>
send_resolved: true
http_config:
authorization:
type: Bearer
credentials: <WEBHOOK_SECRET>Add the receiver to your route tree. Alerts can go to Kollaber as well as to your existing paging receiver.
route:
receiver: pagerduty
routes:
- receiver: kollaber
continue: trueEach entry in the delivery becomes one alert event, timestamped when the alert started rather than when the webhook arrived.
No. Kollaber does not page anyone and evaluates no alert rules. Route alerts to it alongside your pager so the alert is recorded next to the changes around it.
No. Repeat deliveries are deduplicated by fingerprint, so an alert that fires for six hours is one event, not one event per repeat_interval.
The first of service, job, or app that is set, falling back to alertname. Setting a service label on your rules gives the cleanest grouping.
The free plan covers two environments and five members. The full reference for this integration lives in the docs.