acktide.
Menu

Connect your monitoring sources

Your monitoring sends an alert. Acktide finds the engineer on call.

Choose an integration, create a source in Acktide and give its URL to your monitoring system. Keep existing notification channels running in parallel if needed.

Prometheus / Alertmanager

Create an Alertmanager source. Save its URL in /etc/alertmanager/acktide.url, readable by the Alertmanager process, and add a receiver:

receivers:
  - name: acktide
    webhook_configs:
      - url_file: /etc/alertmanager/acktide.url
        send_resolved: true

Route the relevant events to this receiver using route. send_resolved sends recovery events. Labels such as team: kafkacan be used for routing in Acktide. Before applying the configuration, validate it with amtool check-config.

Connect and test your first alert →

Zabbix

A ready-to-import webhook media type is available for Zabbix 7. It sends problem and recovery events with an event ID, hostname and severity.

  1. Create a Zabbix source in Acktide and copy its webhook URL.
  2. Download the template below. In Zabbix, open Alerts → Media types → Import and import the YAML.
  3. Add the Acktide media type to a user. Paste the source URL into Send to.
  4. Enable problem and recovery notifications in the action. Test both events.
Download the Zabbix 7 media type

This template is for Zabbix 7. Test problem and recovery events on your version before using it in production.

Grafana Alerting

  1. Create a Grafana source in Acktide.
  2. In Grafana, open Alerting → Contact points and create a Webhook contact point.
  3. Enter the source URL, select POST and enable recovery messages.
  4. Assign the contact point to a notification policy and send a test event.

The standard Grafana format works without a custom JSON template. A provisioning YAML is also available: replace the URL with your source URL and keep the file secret.

Download the provisioning template

Sentry

  1. Create a Sentry source in Acktide.
  2. In your Sentry integration settings, use the provided webhook URL as the event handler address.
  3. Enable issue events or the relevant issue alert rule and attach the integration.
  4. Trigger a test error and check the alert in Acktide. For automatic resolution, enable issue lifecycle events, including resolved.

Acktide accepts issue and issue alert events. Available settings depend on your integration type and Sentry version.

Connect your own service through a webhook

Create a Generic webhook source. Send event_id for deduplication, a stable fingerprint for each incident, and status: firing or resolved.

{
  "event_id": "payments-check-001",
  "fingerprint": "payments-api-errors",
  "title": "Payments API: error rate rising",
  "severity": "critical",
  "status": "firing",
  "labels": {
    "team": "payments",
    "service": "payments-api"
  }
}

The console provides the source URL and token. Keep them out of tickets, screenshots and public repositories. After connecting, check the alert card, phone notification, ACK and resolution.

Test delivery and acknowledgment →