> 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/observability-and-apm.md).

# Observability and APM

This category covers observability platforms and application performance monitoring tools. These tools collect metrics, traces, and logs across your application stack and send alert notifications to I

### Integrations in this category

| Integration     | What it monitors                                         | Alert delivery         |
| --------------- | -------------------------------------------------------- | ---------------------- |
| **Grafana**     | Metrics, logs, traces across any data source             | Webhook                |
| **Prometheus**  | Time-series metrics, service health                      | Webhook (Alertmanager) |
| **Datadog**     | Infrastructure, APM, logs, synthetics                    | Webhook                |
| **New Relic**   | Application performance, infrastructure, browser         | Webhook                |
| **Dynatrace**   | Full-stack observability, AI-powered anomaly detection   | Webhook                |
| **AppDynamics** | Application performance, business transaction monitoring | Webhook                |
| **SignalFX**    | Real-time infrastructure and application metrics         | Webhook                |
| **SigNoz**      | Distributed tracing, metrics, and logs (open source)     | Webhook                |
| **Elastic**     | Logs, metrics, APM, and SIEM alerts                      | Webhook                |
| **Site24x7**    | Servers, applications, websites, cloud resources         | Webhook                |
| **Cortex**      | Multi-tenant Prometheus metrics at scale                 | Webhook                |

***

### How it works

Observability and APM tools continuously evaluate metrics and trace data against alert rules. When a rule fires — an error rate crosses a threshold, a service latency degrades, or an anomaly is detected — the tool sends an alert to your ITOC360 Source webhook URL. ITOC360 maps the incoming payload fields to alert properties, matches the alert against your escalation policies, and routes the incident to the correct on-call engineer.

{% hint style="info" %}
ITOC360 generates a unique webhook URL per Source. Go to **Management > Sources**, create a Source, and copy the webhook URL or token to paste into your tool's alerting configuration.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.itoc360.com/integrations/inbound-integrations/observability-and-apm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.