EvoHub Docs Sign in

Integrations

ManageEngine OpManager

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 OpManager alarms through a notification profile of type Invoke a Webhook. Each alarm opens an EvoHub alert; when OpManager sends the same alarm as Clear, the alert resolves.

Set it up

Create the integration

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

Create the notification profile

In OpManager, go to Settings → Notifications → Notification Profiles → Add and choose Invoke a Webhook. Set the Request URL to your webhook URL, the method to POST and the body type to Raw / JSON, and paste the body below.

Choose the criteria

Select the alarm severities that should page and also the clear criterion. Without it OpManager never tells EvoHub the alarm has cleared.

Associate devices

Apply the profile to the devices or groups to monitor.

{"alarm_id":"$alarmid","entity":"$entity","device":"$displayName","category":"$category","severity":"$stringseverity","message":"$message","event_type":"$eventType","ip":"$DeviceField(ipAddress)","time":"$strModTime"}

Test Action sends the variables without values. EvoHub answers with success and opens no alert.

What EvoHub reads

EvoHub alert Taken from
Title device and event_type, for example core-sw-01 – CPU Utilization.
Description message.
Labels category, ip, device, alarm_id, entity, time, severity.

Severity

OpManager severity EvoHub severity
Critical, Service Down critical
Trouble high
Attention medium
Clear resolves the alert

Resolve and deduplication

An alarm is identified by its entity (the device and monitor). A repeat while the alert is open is recorded as Retriggered; a Clear for the same entity resolves it.

Last updated