EvoHub DocsEvoHub Docs Sign in

IBM Instana

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.evohub.io/mcp

Claude Code

claude mcp add --transport http evohub-docs https://docs.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": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://docs.evohub.io/mcp"
      ]
    }
  }
}

Cursor — ~/.cursor/mcp.json

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

VS Code — .vscode/mcp.json

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

EvoHub receives Instana issues and incidents through a Webhook alert channel. An open issue opens an EvoHub alert, and Instana closing the issue resolves it.

Set it up

Create the integration

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

Add the alert channel

In Instana, open the alert channels settings (Settings → Events & alerts → Alert channels — under Global settings in recent versions), click Add alert channel, choose the generic Webhook type and add your webhook URL.

Test it

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

Use it in alert configurations

Add the channel to the alert configurations (application, infrastructure, website or global alerts) that should page.

Instana's own issue JSON is read as it is.

What EvoHub reads

EvoHub alert Taken from
Title issue.text, plus " on entityLabel" when it is not already in the text.
Description issue.suggestion.
Labels zone, fqdn, entity, entity_label, entity_type, container, service, tags, issue_type, and url (the issue link).
Fingerprint issue.id.

Severity

Instana severity EvoHub severity
10 (critical) critical
5 (warning) medium
no severity, on an incident critical
anything else medium

Resolve and deduplication

  • state: CLOSED resolves the alert for that issue ID.
  • Updates to an open issue are recorded as Retriggered on its alert.
  • Presence events (type: presence): offline opens <entity> on <host> is offline as high, and online for the same entity resolves it. The two events carry different IDs, so the alert is identified by the host, entity type, entity label and container.
  • Change events (type: change) are answered 200 and open nothing: they have no state and never close.

You can also connect Instana through a Prometheus Alertmanager alert channel pointed at a Prometheus integration; see Prometheus. The Webhook channel described here carries more detail.

Last updated Powered by