EvoHub Docs Sign in

Integrations

Honeycomb

Use with AI
View as MarkdownThis page as plain text, for pasting into an AI tool Open in ClaudeAsk Claude questions about this page Open in ChatGPTAsk ChatGPT questions about this page
Connect to Cursor / VS Code / ClaudeSearch and read these docs from your AI tool (MCP server)

MCP server URL

https://docs-dev.evohub.io/mcp

Add to CursorAdd to VS Code

Claude Code

claude mcp add --transport http evohub-docs-docs https://docs-dev.evohub.io/mcp

Claude (claude.ai and Claude Desktop): Settings → Connectors → Add custom connector, and paste the URL above.

Claude Desktop — claude_desktop_config.json

{
  "mcpServers": {
    "evohub-docs-docs": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://docs-dev.evohub.io/mcp"
      ]
    }
  }
}

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "evohub-docs-docs": {
      "url": "https://docs-dev.evohub.io/mcp"
    }
  }
}

VS Code — .vscode/mcp.json

{
  "servers": {
    "evohub-docs-docs": {
      "type": "http",
      "url": "https://docs-dev.evohub.io/mcp"
    }
  }
}

llms.txtllms-full.txt

EvoHub receives Honeycomb trigger notifications through a webhook integration. Honeycomb's default payload is read as it is: a trigger that fires opens an EvoHub alert, and the same trigger returning to OK resolves it.

Set it up

Create the integration

In EvoHub, go to On-Call → Integrations → + Add Integration, choose Honeycomb, pick an Escalation Policy and click Create Integration. Copy the Webhook URL.

Create the webhook

In Honeycomb, go to Team settings → Integrations → Add integration → Webhook. Set Webhook URL to your webhook URL and leave Secret empty — the key in the URL authenticates the call. If you prefer the key out of the URL, remove ?key=… from it and paste the key as the Secret instead.

Test it

Click Test. EvoHub answers with success and opens no alert.

Add it to triggers

In each trigger, add the webhook under Recipients.

What EvoHub reads

EvoHub alert Taken from
Title The trigger name.
Description description, followed by the trigger's own description.
Severity high.
Labels trigger_id, operator, threshold, trigger_url, groups (the groups that crossed the threshold) and url (the query result).

Resolve and deduplication

An alert is identified by the trigger. Repeat firings while it is open are recorded as Retriggered; status OK resolves it.

Last updated