> For the complete documentation index, see [llms.txt](https://docs.itoc360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itoc360.com/integrations/inbound-integrations/infrastructure-monitoring.md).

# Infrastructure Monitoring

This category covers tools that monitor the health of physical and virtual infrastructure: servers, network devices, bandwidth, disk usage, and service availability. When a threshold is breached, these tools send alerts to ITOC360 to trigger on-call notifications.

***

### Integrations in this category

| Integration                | What it monitors                                   | Alert delivery |
| -------------------------- | -------------------------------------------------- | -------------- |
| **Zabbix**                 | Servers, network devices, applications, databases  | Webhook        |
| **PRTG Network Monitor**   | Network bandwidth, uptime, hardware sensors        | Webhook        |
| **SolarWinds Orion**       | Network performance, server health, flow analysis  | Webhook        |
| **ManageEngine OpManager** | Network devices, servers, virtual machines         | Webhook        |
| **CheckMK**                | Hosts, services, containers, cloud resources       | Webhook        |
| **Instana**                | Microservices, Kubernetes, application performance | Webhook        |
| **Salesforce**             | CRM cases, support tickets, workflow alerts        | Apex Trigger   |

***

### How it works

Infrastructure monitoring tools continuously check your hosts and services against defined thresholds. When a threshold is exceeded — a server goes down, CPU spikes, or a network device becomes unreachable — the tool sends an alert payload to your ITOC360 Source webhook URL. ITOC360 parses the payload, matches it against your escalation policies, and notifies the on-call engineer responsible for that infrastructure.

{% hint style="info" %}
ITOC360 generates a unique webhook URL per Source. Go to **Management › Alert sources**, create a Source, and copy the webhook URL or token to paste into your monitoring tool's notification settings.
{% endhint %}

***

### Get started


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.itoc360.com/integrations/inbound-integrations/infrastructure-monitoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
