On-call rotation, without the OpsGenie bill.
Pikett takes alerts from your monitoring, notifies whoever is on call by email, chat, voice and sms, and escalates until someone acknowledges.
Free while in beta. No card asked. Registration asks for a company name, your name and an email address. You sign in with a link sent to that address.
-
5xx rate above 5% for 2 minutesAlertmanager posts the alert. Three more firings in the next minute fold into it.
-
Called Artur - No responseHe is on call this week. Phone call and email.
-
Escalated. Calling JonasSecond rung of the policy, five minutes after the first.
-
Jonas acknowledgesHe presses 1 during the call. The third rung is cancelled.
-
ClosedAlertmanager reports the rate back to normal. Nobody closes it by hand.
How it works
-
Send alerts
Create an integration and point your monitoring at its URL. A repeat of an alert that is still open is counted on that alert and notifies nobody a second time. A resolution from the sender closes it.
-
Notify the person on call
Pikett reads the rota to find who is on call now and notifies them on their contact methods: email, chat, voice and sms.
-
Acknowledge or escalate
The notification carries a link. Acknowledging stops the escalation. If nobody does, the next rung of the escalation policy is notified after its delay.
What can send alerts
Every sender posts over HTTPS to a URL that contains its integration key. Nothing is installed on your side.
- Generic webhook
-
A JSON body you write yourself: a message, an alias that identifies the condition, a priority from P1 to P5, and a status that closes the alert when the condition is over.
It fits any tool whose webhook body you can template, for example Datadog, New Relic, Dynatrace, AppDynamics, Zabbix, Nagios, Icinga 2, PRTG, Kibana, Sumo Logic, SolarWinds Orion, LogicMonitor, Healthchecks.io, Checkly, Honeycomb and UptimeRobot, and a
curlline in a CI job. - Prometheus Alertmanager
Read in Alertmanager's own webhook format. Firing and resolved alerts in a group notification open and close alerts in Pikett.
- Grafana
Grafana Alerting's webhook contact point is read as sent. The legacy dashboard alerting webhook, up to Grafana 8, has its own preset.
- AWS
CloudWatch alarms through an SNS topic with an HTTPS subscription. Pikett answers the subscription handshake;
ALARMopens an alert andOKcloses it. Cost Anomaly Detection topics subscribe the same way.- Vendor presets
-
For senders with a fixed webhook body, a preset reads the vendor's own fields:
Azure Monitor, Google Cloud Monitoring, Uptime Kuma, Pingdom, Site24x7, Rollbar, Netdata, Splunk, Graylog, Cloudflare and Sentry.
- OpsGenie-compatible endpoint
A sender built for the OpsGenie alert API keeps its request format and its
GenieKeyheader. See moving from OpsGenie.- PagerDuty Events v2 compatible endpoint
A sender built for PagerDuty Events API v2 posts to
/v2/enqueuewith a Pikett integration key as itsrouting_key.triggeropens an alert andresolvecloses it.
What you get
-
On-call rotas
Schedules built from rotations, with cover for the shifts somebody swaps. The console shows who is on call now.
-
Escalation policies
A ladder of rungs, each with a delay and somebody to notify. One policy can serve the whole organisation, and a service or an integration can name its own.
-
Acknowledgement by link
The link in a notification opens a screen with one button. Opening the link alone acknowledges nothing, so a mail scanner that follows links cannot silence an alert.
-
Heartbeats
A job pings Pikett on a schedule. When a ping is overdue, Pikett opens an alert and notifies for it like any other.
-
Incidents
Alerts on the same service that arrive close together are grouped into one incident with a timeline.
-
Postmortems
Written in markdown on the incident they account for, and published from there.
-
Reports
How many alerts arrived, how quickly they were acknowledged and resolved, and which services raised the most.
-
Test notifications
Notify yourself on every contact method you have set up, to find a wrong address before an incident does.
Moving from OpsGenie
Pikett answers the OpsGenie v2 calls a sender makes. Change the base URL to https://app.pikett.eu and put a Pikett integration key in the GenieKey header; the request bodies stay as they are.
- Create an alert:
POST /v2/alerts - Close, acknowledge or add a note by alias:
POST /v2/alerts/{alias}/close,/acknowledge,/notes - Ping a heartbeat by name:
/v2/heartbeats/{name}/ping
Alerts are addressed by alias only, and the rest of the OpsGenie API is not served. Rotas, policies and people are set up in Pikett.
Free while in beta.