> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr/insights-and-tips-cortex-xdr/data-and-platform-administration/data-ingestion-health.md).

# Data ingestion health

Learn how Cortex XDR monitors data ingestion health, detects gaps and delays, measures data freshness, and creates custom alerts.

Cortex XDR tracks ingestion for each data source, so you can find gaps and delays before they affect detection.

### Built-in ingestion monitoring

When ingestion monitoring is enabled, Cortex XDR builds a baseline of normal ingestion for each data source. It raises an **Ingestion** health issue when a source stops sending data, or when volume drops significantly below the baseline. Review health issues in **Settings** → **Health Issues**, or in the issues view filtered to the **Health** domain. See [Monitor data ingestion health (BETA)](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/administration-and-troubleshooting/about-health-issues/monitor-data-ingestion-health).

{% hint style="info" %}
Built-in ingestion monitoring is in beta. Automatically generated health issues aren't grouped into cases. To trigger automation, use a correlation rule (see below).
{% endhint %}

### Ingestion metrics

Metrics are calculated in five-minute intervals for each source. They include event and byte counts and rates, and `last_seen`. Query them with XQL:

* `metrics_source`: the raw metrics dataset.
* `metrics_view`: a preset that also includes intervals with zero events. Use it to detect silence.

See [Overview of data ingestion metrics](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/administration-and-troubleshooting/overview-of-data-ingestion-metrics).

### Ingestion latency (data freshness)

Data freshness is the delay between when a log is created at the source (`_time`) and when it's ingested (`_insert_time`). Freshness metrics include the maximum, median, and 90th-percentile delay, so you can spot slow sources. See [Measuring data freshness](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/administration-and-troubleshooting/overview-of-data-ingestion-metrics/measuring-data-freshness).

### Create custom ingestion alerts

To set your own thresholds, such as "no logs from the firewall for 20 minutes", create a correlation rule on `metrics_view`. See [Creating correlation rules to monitor data ingestion health](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/administration-and-troubleshooting/overview-of-data-ingestion-metrics/creating-correlation-rules-to-monitor-data-ingestion-health).

### Other health signals

Parsing errors and collection or connectivity errors (for example, from collectors and Marketplace integrations) also raise health issues. You can configure notifications when a Broker VM goes offline.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xdr/insights-and-tips-cortex-xdr/data-and-platform-administration/data-ingestion-health.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.