IT Operations Management

Monitoring, alerts, CMDB, observability

• Tools: 10
• Connectors: 4

Connectors in this domain

• Datadog
• New Relic
• PagerDuty
• Splunk

Tool reference

itom.alerts.get - Get Alert Details

Retrieve complete alert details including related CIs and events.

• Risk: read - Read-only - safe to call freely
• Supported by: Datadog, PagerDuty, Splunk, New Relic

Input schema

Field	Type	Required	Description
alert_id	string	Yes	-
include_events	boolean	No	Default: true.
include_related	boolean	No	Default: false.

Output schema

Field	Type	Required	Description
ci	object	No	-
id	string	No	-
title	string	No	-
events	array	No	-
source	string	No	-
status	string	No	-
service	object	No	-
severity	string	No	-
created_at	string	No	-
description	string	No	-
acknowledged_at	string	No	-

REST example

curl -X POST 'https://integration-hub.rezolve.ai/api/v1/tools/itom.alerts.get/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":{"alert_id":"string"}}'

MCP example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "itom.alerts.get",
    "arguments": {
      "alert_id": "string"
    }
  }
}

---

itom.alerts.search - Search Infrastructure Alerts

Search for infrastructure and monitoring alerts.

• Risk: read - Read-only - safe to call freely
• Supported by: New Relic, Splunk, PagerDuty, Datadog

Input schema

Field	Type	Required	Description
ci_id	string	No	-
limit	integer	No	Default: 50.
status	string	No	One of: open, acknowledged, resolved.
severity	array	No	-
service_id	string	No	-
created_after	string	No	-

Output schema

Field	Type	Required	Description
alerts	array	No	-
alerts[].id	string	No	-
alerts[].title	string	No	-
alerts[].source	string	No	-
alerts[].status	string	No	-
alerts[].service	object	No	-
alerts[].severity	string	No	-
alerts[].created_at	string	No	-
total_count	integer	No	-

REST example

curl -X POST 'https://integration-hub.rezolve.ai/api/v1/tools/itom.alerts.search/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":{"ci_id":"string","limit":50}}'

MCP example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "itom.alerts.search",
    "arguments": {
      "ci_id": "string",
      "limit": 50
    }
  }
}

---

itom.cis.search - Search Configuration Items

Search the CMDB for configuration items.

• Risk: read - Read-only - safe to call freely
• Supported by: Datadog, New Relic, Splunk, PagerDuty

Input schema

Field	Type	Required	Description
class	string	No	CI class (server, application, database, etc)
limit	integer	No	Default: 50.
query	string	No	-
status	string	No	-
environment	string	No	One of: production, staging, development.

Output schema

Field	Type	Required	Description
cis	array	No	-
cis[].id	string	No	-
cis[].name	string	No	-
cis[].class	string	No	-
cis[].status	string	No	-
cis[].attributes	object	No	-
cis[].environment	string	No	-
total_count	integer	No	-

REST example

curl -X POST 'https://integration-hub.rezolve.ai/api/v1/tools/itom.cis.search/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":{"class":"string","limit":50}}'

MCP example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "itom.cis.search",
    "arguments": {
      "class": "string",
      "limit": 50
    }
  }
}

---

itom.dashboards.list - List Dashboards

List monitoring dashboards

• Risk: read - Read-only - safe to call freely
• Supported by: Datadog, New Relic, Splunk, PagerDuty

Input schema

Field	Type	Required	Description
limit	number	No	-

Output schema

No fields.

REST example

curl -X POST 'https://integration-hub.rezolve.ai/api/v1/tools/itom.dashboards.list/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":{"limit":0}}'

MCP example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "itom.dashboards.list",
    "arguments": {
      "limit": 0
    }
  }
}

---

itom.incidents.escalate - Escalate Incident

Escalate an incident to next responder

• Risk: write - Creates or modifies data
• Supported by: PagerDuty, Datadog, Splunk, New Relic

Input schema

Field	Type	Required	Description
incident_id	string	No	-

Output schema

No fields.

REST example

curl -X POST 'https://integration-hub.rezolve.ai/api/v1/tools/itom.incidents.escalate/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":{"incident_id":"string"}}'

MCP example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "itom.incidents.escalate",
    "arguments": {
      "incident_id": "string"
    }
  }
}

---

itom.incidents.suspected_major.list - List Suspected Major Incidents

List potential major incidents based on alert correlation.

• Risk: read - Read-only - safe to call freely
• Supported by: PagerDuty, Splunk, Datadog, New Relic

Input schema

Field	Type	Required	Description
limit	integer	No	Default: 20.
include_resolved	boolean	No	Default: false.
min_impact_score	number	No	Minimum impact score (0-1) Default: 0.7.

Output schema

Field	Type	Required	Description
suspected_majors	array	No	-
suspected_majors[].id	string	No	-
suspected_majors[].title	string	No	-
suspected_majors[].detected_at	string	No	-
suspected_majors[].impact_score	number	No	-
suspected_majors[].related_alerts	integer	No	-
suspected_majors[].affected_services	array	No	-

REST example

curl -X POST 'https://integration-hub.rezolve.ai/api/v1/tools/itom.incidents.suspected_major.list/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":{"limit":20,"include_resolved":false}}'

MCP example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "itom.incidents.suspected_major.list",
    "arguments": {
      "limit": 20,
      "include_resolved": false
    }
  }
}

---

itom.logs.search - Search Logs

Search application and infrastructure logs

• Risk: read - Read-only - safe to call freely
• Supported by: Datadog, Splunk, New Relic, PagerDuty

Input schema

Field	Type	Required	Description
to	string	No	-
from	string	No	-
query	string	No	-

Output schema

No fields.

REST example

curl -X POST 'https://integration-hub.rezolve.ai/api/v1/tools/itom.logs.search/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":{"to":"string","from":"string"}}'

MCP example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "itom.logs.search",
    "arguments": {
      "to": "string",
      "from": "string"
    }
  }
}

---

itom.oncall.get - Get On-Call Schedule

Get details of an on-call schedule

• Risk: read - Read-only - safe to call freely
• Supported by: PagerDuty, Datadog, Splunk, New Relic

Input schema

Field	Type	Required	Description
schedule_id	string	No	-

Output schema

No fields.

REST example

curl -X POST 'https://integration-hub.rezolve.ai/api/v1/tools/itom.oncall.get/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":{"schedule_id":"string"}}'

MCP example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "itom.oncall.get",
    "arguments": {
      "schedule_id": "string"
    }
  }
}

---

itom.oncall.list - List On-Call Schedules

List on-call schedules and rotations

• Risk: read - Read-only - safe to call freely
• Supported by: PagerDuty, Splunk, Datadog, New Relic

Input schema

Field	Type	Required	Description
team_id	string	No	-

Output schema

No fields.

REST example

curl -X POST 'https://integration-hub.rezolve.ai/api/v1/tools/itom.oncall.list/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":{"team_id":"string"}}'

MCP example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "itom.oncall.list",
    "arguments": {
      "team_id": "string"
    }
  }
}

---

itom.services.list - List Monitored Services

List all services being monitored.

• Risk: read - Read-only - safe to call freely
• Supported by: New Relic, Splunk, PagerDuty, Datadog

Input schema

Field	Type	Required	Description
tier	string	No	One of: tier1, tier2, tier3.
limit	integer	No	Default: 100.
status	string	No	One of: operational, degraded, outage, maintenance.

Output schema

Field	Type	Required	Description
services	array	No	-
services[].id	string	No	-
services[].name	string	No	-
services[].tier	string	No	-
services[].owner	object	No	-
services[].status	string	No	-
services[].description	string	No	-
services[].open_alerts	integer	No	-

REST example

curl -X POST 'https://integration-hub.rezolve.ai/api/v1/tools/itom.services.list/execute' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"input":{"tier":"tier1","limit":100}}'

MCP example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "itom.services.list",
    "arguments": {
      "tier": "tier1",
      "limit": 100
    }
  }
}