Integrations5 min read

Integrations

Connect OpsKnight with 20+ monitoring tools, Slack, and custom webhooks

Integrations

OpsKnight integrates with your entire monitoring and observability stack, routing alerts from any tool to the right people at the right time.


Why Integrations Matter

Your infrastructure is monitored by many tools — APM, uptime monitoring, error tracking, CI/CD pipelines, and more. Without integration:

  • Alerts are scattered across multiple dashboards
  • There's no unified view of what's happening
  • On-call routing is inconsistent
  • Response times suffer

OpsKnight integrations solve this by:

  • Centralizing all alerts in one place
  • Normalizing formats so every alert looks consistent
  • Routing intelligently based on service and urgency
  • Deduplicating to reduce noise

Integration Categories

Alert Sources (Inbound)

These tools send alerts TO OpsKnight:

Category Tools
APM & Monitoring Datadog, New Relic, Dynatrace, AppDynamics
Infrastructure AWS CloudWatch, Azure Monitor, Google Cloud Monitoring
Metrics & Alerting Prometheus/Alertmanager, Grafana
Error Tracking Sentry
Uptime Monitoring UptimeRobot, Pingdom, Better Uptime, Uptime Kuma
Log Analysis Splunk, Elastic
Observability Honeycomb, Splunk Observability
CI/CD GitHub Actions, Bitbucket Pipelines
Custom Generic Webhooks, Events API

Notification Channels (Outbound)

These tools receive notifications FROM OpsKnight:

Channel Purpose
Slack Team channels with interactive buttons
Email Direct inbox notifications
SMS Urgent alerts via text message
Push Mobile app notifications
WhatsApp Messaging alerts
Webhooks Custom HTTP integrations

Quick Start: Connect Your First Tool

Step 1: Choose Your Integration

  1. Go to SettingsIntegrations
  2. Find your monitoring tool
  3. Click Add Integration

Step 2: Copy the Webhook URL

OpsKnight generates a unique webhook URL for each integration:

https://your-opsknight.com/api/integrations/datadog?key=int_abc123

Step 3: Configure Your Monitoring Tool

Paste the webhook URL into your monitoring tool's notification settings.

Step 4: Send a Test Alert

Trigger a test alert to verify the integration is working.


Supported Integrations

APM & Application Monitoring

Datadog

Full-stack monitoring with APM, infrastructure metrics, and logs.

Endpoint: /api/integrations/datadog
Supports: Monitors, Synthetics, APM alerts

New Relic

Application performance monitoring and infrastructure.

Endpoint: /api/integrations/newrelic
Supports: Alert policies, incidents, synthetics

Dynatrace

AI-powered full-stack observability.

Endpoint: /api/integrations/dynatrace
Supports: Problems, anomaly detection

AppDynamics

Business-aware application performance management.

Endpoint: /api/integrations/appdynamics
Supports: Health rules, policy violations

Grafana

Visualization and alerting platform.

Endpoint: /api/integrations/grafana
Supports: Alert notifications

Honeycomb

Observability for distributed systems.

Endpoint: /api/integrations/honeycomb
Supports: Triggers

Sentry

Error tracking and performance monitoring.

Endpoint: /api/integrations/sentry
Supports: Issues, errors, performance alerts

Splunk Observability

Splunk's observability platform.

Endpoint: /api/integrations/splunk-observability
Supports: Detectors, alerts

Elastic / Kibana

Elasticsearch and Kibana alerting.

Endpoint: /api/integrations/elastic
Supports: Watcher alerts, Kibana alerting

Infrastructure & Cloud

AWS CloudWatch

Native AWS monitoring and alerting.

Endpoint: /api/integrations/cloudwatch
Supports: CloudWatch Alarms via SNS

Azure Monitor

Microsoft Azure monitoring service.

Endpoint: /api/integrations/azure-monitor
Supports: Alerts, action groups

Google Cloud Monitoring

GCP native monitoring (formerly Stackdriver).

Endpoint: /api/integrations/gcp-monitoring
Supports: Alerting policies

Metrics & Alerting

Prometheus/Alertmanager

Open-source metrics and alerting.

Endpoint: /api/integrations/prometheus
Supports: Alertmanager webhooks

Uptime Monitoring

UptimeRobot

Website and API uptime monitoring.

Endpoint: /api/integrations/uptimerobot
Supports: Monitor alerts (down/up)

Pingdom

Website uptime and performance monitoring.

Endpoint: /api/integrations/pingdom
Supports: Uptime checks, transaction checks

Better Uptime

Modern uptime monitoring with status pages.

Endpoint: /api/integrations/betteruptime
Supports: Monitor incidents

Uptime Kuma

Self-hosted uptime monitoring.

Endpoint: /api/integrations/uptimekuma
Supports: Monitor notifications

Log & Event Analysis

Splunk On-Call

Incident management from Splunk.

Endpoint: /api/integrations/splunk-oncall
Supports: Alerts, incidents

CI/CD & DevOps

GitHub

GitHub Actions and repository events.

Endpoint: /api/integrations/github
Supports: Workflow failures, security alerts

Bitbucket

Bitbucket Pipelines and repository events.

Endpoint: /api/integrations/bitbucket
Supports: Pipeline failures

Communication

Slack

Team communication with interactive incident management.

  • Rich message formatting with incident details
  • Interactive buttons: Acknowledge, Resolve, View
  • Thread updates for incident timeline
  • Channel-based routing

Full Setup Guide →


Custom Integrations

Generic Webhooks

Connect any tool that can send HTTP webhooks.

Endpoint: /api/integrations/webhook
Supports: Any JSON payload

Events API

Programmatically create and manage incidents.

Endpoint: /api/events
Supports: trigger, acknowledge, resolve actions

Events API Reference →


How Integrations Work

The Alert Flow

┌─────────────────────────────────────────────────────────────────────┐
│                        MONITORING TOOLS                              │
│   Datadog • Prometheus • CloudWatch • Sentry • GitHub • Custom       │
└──────────────────────────────┬──────────────────────────────────────┘
                               │
                               │ Webhook POST
                               ▼
┌─────────────────────────────────────────────────────────────────────┐
│                      OPSKNIGHT INTEGRATION                           │
│   1. Receive webhook payload                                         │
│   2. Verify signature (if configured)                                │
│   3. Parse and normalize event                                       │
│   4. Map to service via routing key                                  │
│   5. Deduplicate using dedup_key                                     │
└──────────────────────────────┬──────────────────────────────────────┘
                               │
                               ▼
┌─────────────────────────────────────────────────────────────────────┐
│                        INCIDENT CREATED                              │
│   - Title, description, urgency extracted                            │
│   - Service assigned                                                 │
│   - Escalation policy triggered                                      │
│   - On-call person notified                                          │
└─────────────────────────────────────────────────────────────────────┘

Payload Normalization

Each integration has a custom parser that normalizes tool-specific formats:

Datadog Alert:

{
  "title": "[Triggered] CPU High on web-01",
  "alert_type": "error",
  "tags": ["env:production", "team:platform"]
}

Normalized to OpsKnight:

{
  "title": "CPU High on web-01",
  "description": "CPU usage exceeded threshold",
  "urgency": "HIGH",
  "source": "datadog",
  "dedup_key": "datadog-alert-12345"
}

Deduplication

The dedup key prevents duplicate incidents from the same root cause:

  1. Same dedup key → Updates existing incident
  2. New dedup key → Creates new incident

This is crucial during alert storms when the same issue triggers multiple alerts.

Last updated for v1

Edit this page on GitHub