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

# Analyze consumption

> Use the license consumption tools to analyze consumption across partitions to understand what's driving growth and detect unwanted spikes.

After [creating partitions](/control/consumption/partitions), use the
[**Consumption**](#analyze-with-the-consumption-page) page to analyze consumption
across partitions to detect unwanted spikes and understand what's driving growth.

The Consumption page displays persisted data consumption against license capacity.
This page also includes panels with alerting details and statuses for individual
budgets, provides a consolidated view of consumption statistics, and displays a
comprehensive list of child partitions and their growth trends.

Use this page to monitor data consumption against your contract, including the
consumption by volume over time and the consumption of each
[partition](/control/consumption/partitions) and any defined
[budgets](/control/consumption/budgeting).

If you have already configured budgets, use the Consumption page to review budget
[thresholds](/control/consumption/budgeting#threshold-types), which help detect
growth patterns in partitions. This information can help to manage both anomalous
spikes in data and slow data growth over time.

## Analyze with the Consumption page

To analyze data consumption in the Consumption page, in the navigation menu, click
**<Icon icon="shield-user" /> Go to Admin** and then select
**<Icon icon="shapes" /> Control <span aria-label="and then">></span> Consumption**.

In the **Consumption** page, use the provided panels to help analyze consumption:

* Use the **Global Partition** panel group to view totals for the global partition
  over the selected time range, including **Consumed** and **Dropped by budgets**.
  When you select a child partition, the panel group is named for that partition.

* In the **Consumption** panel, use the **Time window** menu to review cumulative
  consumption trends across various time windows and partitions to understand what's
  driving growth.

  If you defined [thresholds](/control/consumption/budgeting#threshold-types), a
  dotted line displays on the graph to indicate the threshold value. Use this menu
  to view total consumption for each partition for the selected time period:

  * The **Per second** period helps detect data spikes in real time.
  * The **Daily**, **Weekly**, and **Monthly (Cumulative)** periods help identify
    gradual usage growth or sustained overconsumption patterns in cumulative volumes.
  * The rolling periods help identify recurring anomalies in volume over rolling time
    windows. Choose a shorter period such as **Rolling 30 minutes**,
    **Rolling 1 hour**, or **Rolling 3 hours**, or a longer period such as
    **Rolling 1 day** or **Rolling 7 days** to see broader trends.

* In the **Consumption** panel, use the **Group by** menu to select
  **Consumed by partition** to view total consumption for each partition for the
  selected time period. This view helps to understand which partitions are consuming
  the most of your budget.

* Use the **Budgets** panel to view the status of the selected partition's budget,
  which can be **Ok**, **Alerting**, or **Dropping**, and to review which thresholds
  are approaching or exceeding their limits. A partition with no budget displays no
  status badge.

  <Note>
    The budget for the `global` partition might exceed its threshold, while budgets
    for all child partitions are within their defined thresholds. For the `global`
    partition budget to more accurately reflect growth trends, set thresholds on
    budgets for individual partitions.
  </Note>

* Click the links in the **Child Partitions** section to select individual child
  partitions and display their consumption information. The
  **Current budget status** column reports the status of each child partition's
  budget. Use this view to investigate partitions that are alerting or dropping data.

## Next steps

Based on your findings, you might want to refine your
[partitions](/control/consumption/partitions) with more granular dimensions, such as
adding more child partitions to apply greater levels of control.

After analyzing your consumption and refining partitions, create
[budgets](/control/consumption/budgeting) to apply optional shaping policies that you
can attach to a partition to provide guardrails to avoid usage overages and
overspending.