Skip to main content

Integrations

OpsWorker connects with the tools your team already uses. Integrations fall into three categories:

  • Alert sources — systems that send alerts to OpsWorker via webhook (Prometheus AlertManager, Grafana Alerting, Datadog).
  • Observability and source-control queries — systems OpsWorker queries during investigations and chat (Grafana MCP, Kubernetes MCP, GitHub, GitLab).
  • Notification and AI backend — Slack delivery and the LLM that powers investigation reasoning.

Each integration is configured independently. You can use any combination — start with one alert source and add more as needed.


☸️ Kubernetes

Connect EKS, AKS, GKE, or self-hosted Kubernetes clusters to OpsWorker for AI-powered investigation and chat.

Browse →

🔔 Alerting

Forward alerts from Prometheus AlertManager, Grafana Alerting, or Datadog to trigger OpsWorker investigations.

Browse →

📈 Grafana MCP

Let OpsWorker query Grafana during investigations and chat — PromQL, LogQL, dashboards, alert rules, and incidents.

Read more →

💬 Slack

Receive investigation results, alerts, and OpsWorker notifications directly in your Slack workspace.

Read more →

🐙 GitHub

Connect GitHub to enable the Git AI Agent and allow OpsWorker to open pull requests with suggested fixes.

Read more →

🦊 GitLab

Connect GitLab repositories to correlate deployments with incidents and automate fix MR creation.

Read more →

🧠 LLM / AI Backend

Use your own LLM — AWS Bedrock, Azure OpenAI, or a custom OpenAI-compatible endpoint via the Custom Reasoning Model integration.

Browse →

Grafana: Two Distinct Integrations

Grafana shows up in two places because it serves two different purposes:

IntegrationDirectionPurpose
Grafana AlertingGrafana → OpsWorkerSend alerts to OpsWorker via webhook
Grafana MCPOpsWorker → GrafanaLet OpsWorker query metrics, logs, dashboards

They are independent — you can use one, both, or neither. Both are configured from the Grafana integration page.