> 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/tips-weekly/week-43.md).

# Week 43

**Get alerted when a data source goes quiet**

A data source that stops sending logs creates a blind spot that's easy to miss. In Cortex XSIAM, create a correlation rule on the `metrics_view` preset that triggers when `total_event_count` adds up to zero for a source. Run it on a schedule that fits the source, such as every 20 minutes for firewalls, and generate the issue in the **Health** domain. You'll catch silent data sources before they affect detection.

🔗 [Create correlation rules to monitor data ingestion health](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/administration-and-troubleshooting/overview-of-data-ingestion-metrics/creating-correlation-rules-to-monitor-data-ingestion-health.md)

**Put your case response on autopilot**

Manually investigating every analytics issue creates fatigue and slows down response times. In Cortex XSIAM, Autonomous Playbooks automatically investigate and respond to Cortex Analytics issues (across SSO, EDR, Azure, ITDR, and more) with zero maintenance or custom playbook building required. Currently enabled for new tenants created on or after May 31st, 2026. Contact Customer Support to add it to an existing tenant.\
🔗 [Autonomous playbooks](/cortex-xsiam/configure-cortex-xsiam/automations/autonomous-playbooks.md)


---

# 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/tips-weekly/week-43.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.