Integrations

OpsKnight integrates natively with your entire monitoring, metrics, cloud infrastructure, CI/CD, and observability stack — normalizing payloads and routing alerts to the right on-call engineers in real time.

⚡ Integration Categories

Alert Sources (Inbound)

These tools send telemetry and incident alerts TO OpsKnight:

Notification Channels (Outbound)

These channels dispatch urgent incident notifications FROM OpsKnight:

🔌 Supported Inbound Integrations

1. APM & Application Monitoring

Datadog

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

• Endpoint: /api/integrations/datadog
• Payloads: Monitors, Synthetics, APM alerts

New Relic

Application performance monitoring and infrastructure alerts.

• Endpoint: /api/integrations/newrelic
• Payloads: Alert policies, NRQL violations, synthetics

Dynatrace

AI-powered full-stack observability and problem detection.

• Endpoint: /api/integrations/dynatrace
• Payloads: Problems, anomaly detection, root cause analysis

AppDynamics

Application performance management and business transactions.

• Endpoint: /api/integrations/appdynamics
• Payloads: Health rules, policy violations

Grafana

Grafana Unified Alerting and legacy dashboard alerts.

• Endpoint: /api/integrations/grafana
• Payloads: Unified alerting webhooks, legacy alerts

Honeycomb

Observability and distributed tracing triggers.

• Endpoint: /api/integrations/honeycomb
• Payloads: Triggers, query results

Sentry

Real-time error tracking and performance monitoring.

• Endpoint: /api/integrations/sentry
• Payloads: Issue alerts, metric alerts, webhook events

Splunk Observability

Splunk APM and infrastructure detector alerts.

• Endpoint: /api/integrations/splunk-observability
• Payloads: Detectors, signalflow alerts

2. Cloud & Infrastructure

AWS CloudWatch

Native AWS alarm notifications via Amazon SNS.

• Endpoint: /api/integrations/cloudwatch
• Payloads: CloudWatch Alarms (ALARM, OK, INSUFFICIENT_DATA), SNS subscriptions

Azure Monitor

Microsoft Azure Monitor alerts and Common Alert Schema.

• Endpoint: /api/integrations/azure-monitor
• Payloads: Metric alerts, log search alerts, activity log alerts

Google Cloud Monitoring

Google Cloud Monitoring incident webhooks (formerly Stackdriver).

• Endpoint: /api/integrations/gcp-monitoring
• Payloads: Alerting policies, condition triggers

3. Metrics, Alerting & Server Daemons

Prometheus / Alertmanager

Grouped metric alerts and resolution notifications.

• Endpoint: /api/integrations/prometheus
• Payloads: Prometheus Alertmanager grouped alerts

Zabbix (New in v1.3)

Enterprise server, network, and VM monitoring.

• Endpoint: /api/integrations/zabbix
• Payloads: Trigger events, problem state updates, recoveries (Disaster, High, Average, Warning, Information)

Nagios Core & XI (New in v1.3)

Host and service state alerting with macro variable parsing.

• Endpoint: /api/integrations/nagios
• Payloads: Host alerts (DOWN, UP), Service alerts (CRITICAL, WARNING, OK)

Icinga 2 (New in v1.3)

Modern daemon and distributed check results.

• Endpoint: /api/integrations/icinga
• Payloads: Service check results, host notifications, downtime transitions

4. CI/CD & DevOps

GitHub Actions

Workflow run failures, security alerts, and deployment events.

• Endpoint: /api/integrations/github
• Payloads: workflow_run.completed (failure), repository vulnerability alerts

GitLab CI/CD (New in v1.3)

Pipeline failure tracking with commit and branch resolution.

• Endpoint: /api/integrations/gitlab
• Payloads: Pipeline Hook (failed, success), Job Hook

Bitbucket Pipelines

Bitbucket build statuses and pull request pipelines.

• Endpoint: /api/integrations/bitbucket
• Payloads: repo:commit_status_updated (FAILED, SUCCESSFUL)

Vercel Deployments (New in v1.3)

Frontend build failures and deployment error monitoring.

• Endpoint: /api/integrations/vercel
• Payloads: deployment.error, deployment.canceled

5. Uptime & Synthetic Monitoring

UptimeRobot

Website and API uptime checks.

• Endpoint: /api/integrations/uptimerobot
• Payloads: Monitor alert webhooks (down/up)

Pingdom

Global synthetic uptime checks and transaction monitoring.

• Endpoint: /api/integrations/pingdom
• Payloads: Uptime check state transitions

Better Uptime

Synthetic monitoring and heartbeats.

• Endpoint: /api/integrations/betteruptime
• Payloads: Incident webhook notifications

Uptime Kuma

Self-hosted monitoring and container health checks.

• Endpoint: /api/integrations/uptimekuma
• Payloads: Notification webhooks (down/up)

6. Log Analytics & SIEM

Elastic / Kibana

Elasticsearch cluster and Kibana rule alerting.

• Endpoint: /api/integrations/elastic
• Payloads: Kibana Alerting webhooks, Watcher alerts

Splunk On-Call

Log search alerts and security incident forwarding.

• Endpoint: /api/integrations/splunk-oncall
• Payloads: Alert notifications, incident events

7. Issue Tracking & Project Management

Jira Cloud

Bi-directional Jira integration for real-time ticket creation and comments.

• Endpoint: /api/integrations/jira
• Capabilities: Auto-create Jira issues, route by service, sync comments, manage postmortem action items

8. Custom Integrations & Emulation

PagerDuty Emulation (Events API v2) (New in v1.3)

Drop-in replacement for PagerDuty Events API v2.

• Endpoint: /api/integrations/pagerduty (and /api/events/v2)
• Capabilities: Seamlessly connect any tool with built-in PagerDuty support with 0 code modifications

Generic Webhooks

Connect custom scripts, internal cron jobs, or proprietary systems.

• Endpoint: /api/integrations/webhook
• Capabilities: Custom JSON mapping, HMAC-SHA256 signature verification

🛠️ How Normalization & Deduplication Work

flowchart LR
    Ingress[Inbound Webhook] --> Verify[HMAC / Secret Verification]
    Verify --> Parse[Normalized Event Parser]
    Parse --> Dedup[SHA-256 Fingerprinting Engine]
    Dedup --> Route[Service & Escalation Routing]
    Route --> Dispatch[On-Call Alerting]

1. Verification: Inbound requests are validated via HMAC signatures (X-Hub-Signature-256, X-Grafana-Signature, etc.) or token headers.
2. Normalization: Diverse payload schemas are transformed into OpsKnight's unified incident format (title, description, urgency, service, dedup_key).
3. Deduplication: SHA-256 hashes prevent alert storms from opening duplicate tickets for ongoing root-cause events.
4. Escalation Routing: Active on-call responders receive notifications across Slack, Push, SMS, and Email according to their team schedule.