> 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/log-management.md).

# Log Management

This category covers log aggregation and time-series data platforms. These tools store and analyze large volumes of log and metric data, and send alerts to ITOC360 when log-based conditions or metric thresholds are met.

***

### Integrations in this category

| Integration       | What it monitors                               | Alert delivery        |
| ----------------- | ---------------------------------------------- | --------------------- |
| **Grafana Loki**  | Log aggregation and query-based alerts         | Webhook (via Grafana) |
| **Grafana Mimir** | Long-term Prometheus metrics storage           | Webhook (via Grafana) |
| **Graylog**       | Centralized log management, event streams      | Webhook               |
| **InfluxDB**      | Time-series metrics and threshold-based alerts | Webhook               |

***

### How it works

Log management platforms collect and index log streams from your infrastructure and applications. When a log-based alert rule is triggered — an error pattern appears, a metric threshold is breached, or an anomaly is detected — the platform sends an alert payload to your ITOC360 Source webhook URL. ITOC360 parses the incoming alert, applies escalation logic, and notifies the on-call engineer.

{% hint style="info" %}
Grafana Loki and Grafana Mimir route alerts through Grafana's alerting engine. Configure the ITOC360 webhook as a Grafana contact point to forward alerts from both sources.
{% 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/log-management.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.
