Integrations
Plugs into the stack you already run.
Alertmanager, Grafana and webhooks on the way in. PagerDuty and incident.io on the way out. Each one is labelled honestly: in the beta, being built, or planned.
Sources and destinations
Showing 8 integrations
- In the betaSource
Alertmanager
Add a webhook receiver with send_resolved: true. Firing and resolved alerts both come through.
- In the betaSource
Grafana Alerting
A webhook contact point. Same URL, same grouping.
- In the betaSource
Any JSON webhook
Send JSON from anything that can POST. Field mapping for severity and service is being refined with design partners.
- PlannedSource
More sources
Datadog, CloudWatch, uptime and error tracking. Design partners decide the order.
- Being builtDestination
PagerDuty
Events API v2, with a stable dedup key per group so a resolve in BlipLite resolves the incident. Shadow mode shows what it would send today.
- Being builtDestination
incident.io
An HTTP alert source, firing and resolved, deduplicated. Shadow mode shows what it would send today.
- PlannedDestination
Opsgenie
If design partners need it.
- PlannedDestination
Slack and email digests
For alerts that should be read in the morning, not paged at night.
One receiver, alongside what you have.
Add BlipLite as the first route with continue: true. It gets a copy of every alert; your existing routes keep paging exactly as before.
In Grafana, add a webhook contact point with the same URL and a notification policy that continues matching.
receivers:
- name: bliplite
webhook_configs:
- url: https://<your-bliplite-app>/api/ingest/<source-secret>
send_resolved: true
route:
routes:
# First in the list: BlipLite gets a copy, then your existing routes carry on.
- receiver: bliplite
continue: trueDon't see your tools?
Design partners decide what gets built next. Tell us what you run when you request access.