> 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-xsiam/detect-investigate-and-respond-to-threats/monitor-dashboards-and-reports/dashboard-reference/command-center-reference/xsiam-command-center/dynamic-view.md).

# Dynamic View

Use Cortex XSIAM Dynamic View to monitor changing security data and operational insights.

The **Dynamic View** provides an overview of Cortex XSIAM activity in real-time. You can see the data sources that are sending data to Cortex XSIAM, data sources with connection errors, playbooks being triggered, and the issues and cases being created.

To access the **Dynamic View** click on the concentric circle in the **XSIAM Command Center**. The **Dynamic View** includes the concentric circle, the live feed, and the key performance indicators. The following table describes each of these sections:

<table><thead><tr><th width="139">Section</th><th>Details</th></tr></thead><tbody><tr><td>Concentric circle</td><td><p>Shows an animation of Cortex XSIAM activity in real-time. Icons represent issues and cases. Data sources are displayed on the outside of the circle, and are color coordinated to represent their connection status. The center of the circle displays statistics about open cases, automatically resolved cases, and manually resolved cases.</p><p>Click on any of the elements to drilldown to dedicated pages for further investigation.</p></td></tr><tr><td>Live feed</td><td><p>Reports the following types of activity on the tenant:</p><ul><li>An issue is added to a case.</li><li>A case is created, resolved, or reopened.</li><li>A playbook is triggered.</li><li>A data source ingested data.</li><li>A data source is in error status.</li></ul><p>Click on any of the live feed elements to link to dedicated pages that can assist you with your investigation.</p></td></tr><tr><td>Key performance indicators</td><td><p>Displays information about data ingested during the time frame, and the number of open cases. The ingestion rate trend percentage is calculated by comparing the ingestion total of the current time frame with the ingestion total of the previous time frame. An arrow indicates whether the rates are rising or falling in comparison to the previous time frame's total.</p><p>Click on the key performance indicators to drilldown to dedicated pages for further investigation.</p></td></tr></tbody></table>


---

# 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-xsiam/detect-investigate-and-respond-to-threats/monitor-dashboards-and-reports/dashboard-reference/command-center-reference/xsiam-command-center/dynamic-view.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.