> ## Documentation Index
> Fetch the complete documentation index at: https://docs-xcor.paloaltonetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cortex XCOR-managed dashboards

> Learn about dashboards included with and managed by Cortex XCOR.

Palo Alto Networks Cortex XCOR includes several dashboards to visualize
information about itself and its usage within your organization.

For example, Cortex XCOR dashboards let you pin tooltips and view nearby
series when holding the pointer over a tooltip.

To pin a tooltip, click while a tooltip is visible in a dashboard's panel. This
causes the tooltip to persist in place, rather than following the cursor as you
move it across the visualization or disappearing after you move the cursor out of
the panel.

To unpin a tooltip, click the tooltip again.

<Note>
  Cortex XCOR-managed dashboards are read-only. You can't edit or delete these
  dashboards. You can export a managed dashboard's code representation and import
  it as a new dashboard that you can modify, but the imported copy won't receive any
  updates that Cortex XCOR makes to the original managed dashboard.
</Note>

## Ingest dashboards

Use the following dashboards to monitor metric ingestion and health in your
Cortex XCOR tenant.

### Cortex XCOR Health Check

The **Cortex XCOR Health Check** dashboard monitors the stability and efficiency of
telemetry data ingestion in your Cortex XCOR environment. This dashboard
includes the following panels for metrics, change events, logs, and traces:

* The **Uptime Percentages (30d)** panel depicts the trailing 30-day product uptime
  of ingest, query, and console services as a percentage, which provides a snapshot
  of the reliability of Cortex XCOR.
* The **Historical Uptime** panel depicts the product uptime averages over time over
  the past 30 days.

The following panels are also included for metrics data:

* The **Invalid Data Points Rejected** panel visualizes counts of data points that
  fail validation, with separate time series presented for each reason.
* The **Ingest Latency** panel depicts the latency from the moment a metric is
  scraped to the moment it's persisted, with lines for those latencies at notable
  percentiles. This data helps you understand the efficiency and speed of metric
  ingestion, and helps your organization identify and address potential bottlenecks
  by correlating ingestion changes with latency spikes.

### CloudWatch Metrics Ingestion & Health

The **CloudWatch Metrics Ingestion & Health** dashboard displays operational
information about the health of your CloudWatch Metrics Streams integration with
Cortex XCOR. Use this dashboard to ensure that
[CloudWatch metrics are streaming](/ingest/xcor/integrations/server/aws-cloudwatch#cloudwatch-metrics-ingestion-health)
to Cortex XCOR.

### Chronosphere Collectors

The **Chronosphere Collectors** dashboard provides a high-level visualization of
metrics and resources used by Chronosphere Collector instances.

### OpenTelemetry Ingestion & Health

The **OpenTelemetry Ingestion & Health** dashboard provides details about how much
data [OpenTelemetry Collector](/ingest/metrics-traces/otel) instances are ingesting
and how many system resources they're using.

The **Chronosphere OTLP Ingestion** panel group visualizes data on ingested data points
by metric type, transformed data points ingested and rejected by Cortex XCOR,
and OpenTelemetry Protocol (OTLP) API response codes and latency.

The **OpenTelemetry Collector Health** panel group visualizes memory and CPU core usage,
and OpenTelemetry Collector instances by version number. When using [Traces](/control/shaping/sample-traces),
data on trace spans might also be available.

The **OpenTelemetry Collector Exporters** panel group visualizes the number of data points
and trace spans sent, and the failure rates for sending or enqueuing data points
and trace spans. Use these to identify usage and potential bottlenecks in exporters.

The **OpenTelemetry Collector Batch Processor** panel group visualizes the number
of data points or trace spans sent in batches, and the rate of batches being sent
because of hitting batch size triggers or timing out.

The **OpenTelemetry Collector Receivers** panel group visualizes the rates of data points,
trace spans, and log records that the OpenTelemetry Collector accepted and refused.

### Google Cloud Integration Dashboard (GCP)

The **Google Cloud Integration Dashboard (GCP)** provides details about how much
[Google Cloud](/ingest/xcor/integrations/server/gcp) data Cortex XCOR is ingesting.
The dashboard includes Google Cloud service status, API usage against recommended
quotas, metadata about the ingested metrics, and the **Top Metric Descriptors** panel.
This dashboard is available when the Google Cloud metrics integration is enabled for
your tenant.

#### GCP Timeseries API Quota Usage Per Project

The **GCP Timeseries API Quota Usage Per Project** panel in the Google Cloud
Integration Dashboard's **Quota** panel group shows how much of the API quota each
Google Cloud project uses. Use the panel to identify projects that might require a
quota increase. The panel populates after
[configuring Google Cloud metrics](/ingest/xcor/integrations/server/gcp).

## Query dashboards

Use the following dashboards to monitor queries, identify resource intensive alert or
recording groups, and visualize metrics created for traces.

### Query Accelerator

The **Query Accelerator** dashboard visualizes the relative performance of queries
that have been optimized by the Cortex XCOR
[Query Accelerator](/observe/dashboards#query-accelerator) to queries that have
not been optimized. This dashboard is available when Query Accelerator is enabled
for your tenant.

### Trace Metrics

The **Trace Metrics** dashboard visualizes
[metrics created for traces](/control/shaping/sample-traces/trace-metrics).

## Cardinality dashboards

Use the following dashboards to visualize cardinality produced by jobs in a given
namespace, and identify information you can use to help reduce cardinality in your
Cortex XCOR tenant.

### Persisted Cardinality Quotas

The **Persisted Cardinality Quotas** dashboard displays cardinality consumption
breakdown by individual metric pools and priority.
[Persisted cardinality](/administer/limits-licensing/concepts/capacity-licensing#persisted-cardinality)
is a cumulative
measure that calculates the sum of the unique time series of the persisted writes
that Cortex XCOR stores, seen over the last 2.5 hours only.

Use this dashboard to understand cardinality consumption across specific teams,
services, and pools. For organizations that use capacity licensing, the dashboard
includes the following panels, which are backed by specific
[persisted cardinality metrics](/administer/limits-licensing/concepts/capacity-licensing#persisted-cardinality):

* **Total Consumption of License** displays the persisted cardinality consumed across
  all metric pools divided by your persisted license capacity, expressed as a
  percentage.
* **Total Consumption** displays the same data as **Total Consumption of License**,
  plotted on a line graph over the last week.
* **Total Dropped** displays the total metrics dropped during a penalty period if
  your organization exceeds 100% of its Persisted Cardinality Capacity Limit.
* **Consumption of Thresholds** displays the persisted cardinality consumed for each
  configured [pool threshold](/control/shaping/shape-metrics/quotas/define-pools#pool-thresholds),
  and the pool the thresholds are assigned to. This information helps determine
  whether data is being dropped for crossing a defined threshold, rather than
  crossing a hard limit such as a
  [capacity limit](/administer/limits-licensing/concepts/capacity-licensing#capacity-limits).

For capacity licensing, configure
[metric pools](/control/shaping/shape-metrics/quotas/manage-pools) and priorities to display
**Consumption by Pool** and **Consumption by Priority** panels in this dashboard.
This view uses the same pools and priorities configured in your
[Matched Writes Quotas](#matched-writes-quotas) dashboard. If you didn't configure
that dashboard, the **Persisted Cardinality Quotas** dashboard displays persisted
cardinality consumption only.

For organizations that use consumption pricing, the dashboard displays peak
consumption over the selected range for top metric names and configured usage tags.

To further identify sources of cardinality increases, the
**Persisted Cardinality Quotas** dashboard includes panel groups that display top
metrics and values for your most critical usage tags defined in the
[Usage Dashboard](#usage-dashboard). For each of your usage tags, the
**Persisted Cardinality Quotas** dashboard includes two panels:

* A time series chart that displays the top label values
* A bar chart with a percentage breakdown of those values in descending order.

Use this information to identify the top metrics and label values for your usage
statistics that contribute to your persisted cardinality consumption, in addition to
the metrics for your predefined metrics pools.

To modify the usage tags that Cortex XCOR uses to generate the top metrics
and labels that display in the **Persisted Cardinality Quotas** dashboard, contact
[Cortex XCOR Support](/support).

### Cardinality Overview

The **Cardinality Overview** dashboard visualizes the cardinality produced by jobs
in a given namespace. Use this dashboard to understand what jobs are causing high
cardinality, and how the metrics in a job contribute to cardinality.

### Metric Growth

The **Metric Growth** dashboard helps you identify potential sources of metric growth
in your system. This dashboard is available when Metric Growth is enabled for your
tenant. It includes the following panels:

* The **Overview** panel group visualizes the top 10 metrics and labels by volume
  in data points per second (DPPS).
* The **Change Over Comparison Period Using Averages** panel group visualizes the
  metrics and labels with the highest DPPS growth rates over a selected comparison
  period. It also displays labels with the highest growth rates in unique values.
* The **Drilldown** panel group visualizes additional data about metrics or labels
  selected in the dashboard's **drilldownMetric** and **drilldownLabel** template variables.
  Visualized data includes cardinality and DPPS growth over time.

Use this dashboard to understand when:

* A newly added high-cardinality metric or label appears with high DPPS. You can
  understand its impact by comparing it to an older time range.
* An existing metric or label with more unique values appears to have grown in DPPS,
  such as a histogram metric whose buckets greatly increased.

You can then use this information to [reduce cardinality](/control/shaping/shape-metrics/reduce-cardinality).

## Licensing dashboards

Cortex XCOR provides dashboards to monitor data usage against your licensing quotas.
Use these dashboards to help identify usage trends across data types. You can then
proactively manage data usage to avoid exceeding your organization's licensing
limits.

For more information about the licensing terms used on these dashboards, and details
about how Cortex XCOR calculates these values, see
[Licensing concepts](/administer/limits-licensing/concepts/capacity-licensing).

In addition to these dashboards, Cortex XCOR provides a consolidated
[License Overview](/administer/limits-licensing/licensing) page that
contains information about your current license usage and data retention periods.
Unlike other Chronosphere-managed dashboards, you can access this dashboard in the
navigation menu by clicking **<Icon icon="shield-user" /> Go to Admin**, and
then clicking
**<span style={{display: 'inline-block', transform: 'scaleX(-1)'}}><Icon icon="scroll-text" className="fill-current" /></span> License Overview**.

### Consumption System Limits

For organizations that use consumption pricing, consumption system limits protect
the stability of Cortex XCOR by restricting abnormal or unexpectedly
rapid increases in telemetry volume. These limits apply separately from contract
credit consumption and [budgets](/control/consumption/budgeting). Contract credits
determine usage costs, while budgets provide customer-configured alerts and shaping
controls.

The **Consumption System Limits** dashboard is the source of truth for the system
limits enforced in your tenant. In the navigation menu, select **Dashboards**, and
then search for **Consumption System Limits**.

The dashboard includes sections only for the telemetry products and system limits
configured for your tenant. The following system limits can appear:

* Metrics persisted data points per second, evaluated over a rolling 30-minute
  window and presented as a per-second rate.
* Metrics persisted series, measured as the number of series over a rolling
  30-minute window.
* Logs processed bytes per second.
* Logs persisted bytes per second.
* Traces processed bytes per second.

For each system limit, the dashboard provides the following panels:

* The **Usage** panel compares consumed data with the threshold. It also displays
  received data, calculated as consumed data plus data dropped by the system limit.
* The **Dropped** panel displays data dropped because traffic exceeded the system
  limit.

- The **% utilization, last 7d** panel displays average and maximum utilization over
  the trailing seven days. Utilization is consumed data divided by the threshold.

The logs and traces rates use a sliding two-minute window and are presented as
per-second rates. Use the usage and utilization panels to assess available headroom
before a planned increase in telemetry volume. Any nonzero value in a **Dropped**
panel means that the corresponding system limit rejected data.

#### Monitor Consumption System Limits

The metrics that support the Consumption System Limits dashboard are available in
your tenant. The following table lists the threshold, consumed, and dropped metrics
for each system limit:

| System limit | Threshold metric | Consumed metric | Dropped metric |
| - | - | - | - |
| Metrics persisted data points per second | `chrono_metrics_persisted_datapoints_per_second_limit_threshold` | `chrono_metrics_persisted_datapoints_per_second_limit_consumed` | `chrono_metrics_persisted_datapoints_per_second_limit_dropped` |
| Metrics persisted series over 30 minutes | `chrono_metrics_persisted_series_30min_volume_limit_threshold` | `chrono_metrics_persisted_series_30min_volume_limit_consumed` | `chrono_metrics_persisted_series_30min_volume_limit_dropped` |
| Logs persisted bytes per second | `chrono_logs_persisted_bytes_per_second_limit_threshold` | `chrono_logs_persisted_bytes_per_second_limit_consumed` | `chrono_logs_persisted_bytes_per_second_limit_dropped` |
| Logs processed bytes per second | `chrono_logs_processed_bytes_per_second_limit_threshold` | `chrono_logs_processed_bytes_per_second_limit_consumed` | `chrono_logs_processed_bytes_per_second_limit_dropped` |
| Traces processed bytes per second | `chrono_traces_processed_bytes_per_second_limit_threshold` | `chrono_traces_processed_bytes_per_second_limit_consumed` | `chrono_traces_processed_bytes_per_second_limit_dropped` |

[Create a metric monitor](/investigate/alerts/monitors) that divides the consumed
metric by the threshold metric. Set warning and critical conditions based on the
operating headroom your organization requires. For example, the following query
returns usage information for the metrics persisted data points limit:

```text theme={null}
max(chrono_metrics_persisted_datapoints_per_second_limit_consumed)
/
max(chrono_metrics_persisted_datapoints_per_second_limit_threshold)
```

Create a separate condition for dropped data. The following query returns a value
greater than zero when the metrics persisted data points limit drops data:

```text theme={null}
max(chrono_metrics_persisted_datapoints_per_second_limit_dropped) > 0
```

To monitor another system limit, substitute its corresponding consumed, threshold,
and dropped metrics from the preceding table.

#### Adjust Consumption System Limits

If an intentional, sustained increase in telemetry volume requires more capacity,
contact [Cortex XCOR Support](/support) to request an adjustment. Submit the request
at least three business days before the increase. System limit adjustments require
mutual agreement and Palo Alto Networks approval.

### Metrics Query Capacity Overview

The **Metrics Query Capacity Overview** dashboard visualizes query capacity
consumption for automated metric queries against the system capacity. Use this
dashboard to understand automated query usage against query capacity limits. The
reporting metrics include queries from monitors, recording rules, service-level
objectives (SLOs), and service accounts.

See
[automated source query limits](/administer/limits-licensing/limits/query-limits#automated-source-query-limits)
for more information about the limits that this dashboard visualizes.

* The **Overview** panel group displays the total number of query selectors currently
  consumed and dropped versus the system limit, and the number of selectors by source
  type. Other panels in this group display the total data reads per second and
  the number of data reads by source type.
* The **Monitors** panel group displays monitors' query selector usage and data reads
  per second by time interval, and the top collections and slugs by selector usage
  and data reads per second.
* The **Recording Rules** panel group displays recording rules' query selector usage
  and data reads per second by time interval. Other panels list the top execution
  groups, slugs, and output metrics by selector usage and data reads per second.
* The **Service Accounts** panel group displays the top universally unique
  identifiers (UUIDs) by selector usage and data reads per second.
* The **SLOs** panel group displays the slugs of top SLOs by selector usage and data
  reads per second.
* The **Query Resource Pool** panel group displays data read and rejected queries for
  each value of the `pool_name` dashboard variable.

The Metrics Query Capacity Overview dashboard doesn't include contract, budget, or
partition consumption. For organizations that use consumption pricing:

* Use [License Overview](/administer/limits-licensing/licensing) to compare credit
  consumption with your contract.
* Use the [Consumption page](/control/consumption/analyze) to analyze consumed and
  dropped data by partition, review budget status, and select threshold time windows.
* Use [Partitions](/control/consumption/partitions) and
  [budgets](/control/consumption/budgeting) to configure consumption controls.

### Matched Writes Quotas

The **Matched Writes Quotas** dashboard displays matched writes consumption. When the
matched writes capacity limit is enforced, use this dashboard to compare consumption
with pool allocations and the capacity limit, and to review drops by pool and
priority. Use the `pool_name` dashboard variable to display a panel group for each
configured pool.

This dashboard includes a **Summary** panel group containing panels for the following
statistics when the matched writes capacity limit is enforced:

* **Total Consumption of License** displays the current total consumption rate as a
  percentage, which is calculated as the total matched writes consumed divided by the
  license capacity.
* **Total Consumption** displays the consumption rate of matched writes versus your
  total capacity limit for matched writes.
* **Total Dropped by Pool Priority (Stacked)** displays dropped data by pool and
  priority.
* **Consumption by Pool Breakdown** displays matched writes consumption in data points
  per second (DPPS) by pool name.

This dashboard also includes panel groups for each of your defined metric pools. Each
panel group contains panels for the following statistics:

* **Consumption** displays the consumption rate of matched writes for the selected
  pool versus your total capacity limit for matched writes.
* **Consumption by Priority** displays the matched writes consumed in DPPS by
  priority within the pool, separated by low, medium, and high priority data.
* **Dropped by Priority** displays the matched writes dropped in DPPS by priority
  within the pool, separated by low, medium, and high priority data.

When your tenant uses consumption pricing for metrics and the matched writes capacity
limit isn't enforced, the dashboard instead provides a
**Peak Consumption over Range** panel.

See
[matched writes](/administer/limits-licensing/concepts/capacity-licensing#matched-writes)
in the metrics
dictionary for more information about the metrics that Cortex XCOR uses to
create the statistics displayed in this dashboard.

## Usage Dashboard

The **Usage Dashboard** provides a regular breakdown of ingested, persisted, and
dropped metrics across your organization by the usage tags configured for your
tenant. These tags can include labels such as `cluster`, `environment`, `app_name`,
and `service_name`.

Use this dashboard to identify what's contributing the most to your Cortex XCOR
usage, and to manage your overall usage.

The **Usage Dashboard (Histograms)** provides the same type of breakdown for histogram
metrics.


## Related topics

- [Visualize data using dashboards](/observe/dashboards.md)
- [JSON representation format](/observe/dashboards/panels/json-representation.md)
- [Classic dashboards](/observe/dashboards/classic-dashboards.md)
- [Visualize dashboard contents with panels](/observe/dashboards/classic-dashboards/classic-panels.md)
- [Head sampling](/control/shaping/sample-traces/head-sampling.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.