> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/power-monitor/monitoramento/historico-de-consumo.md). # Consumption History Daily timeline of Capacity Units consumption by workspace, workload, or item, with change against the previous window, consumption concentration, per-lane drill-down, and AI analysis. **Consumption History** shows the daily evolution of Capacity Units (s) consumption over a period (from yesterday up to the last 180 days, or a custom range), in **lanes** (*swimlanes*): one lane for the consolidated total and one for each workspace, workload, or item that consumed the most. It is the screen for seeing trends, seasonality (for example, month-end closings), and who is growing. **How to access:** * *Monitoring › Consumption History*; or * *Capacities › Consumption History* (same screen; see [Capacities (menu)](/en/power-monitor/capacidades.md)). The screen is available to **all profiles**. The data considers only capacities with monitoring enabled and respects the user's workspace scope. If an administrator blocks this page for your user, it no longer appears in the menu.

Consumption History screen with KPIs and the lane timeline — Consumption History: lane timeline

## What it is for * **Capacity planning and FinOps:** evaluate the daily average and peak over the last 90 days (or up to 180 days) before deciding on a larger SKU or on reservations. * **Identify who is growing:** the **Biggest movers** card points out the entities that went up (or down) the most compared with the previous window of the same size. * **Understand concentration:** the **Consumption concentration** card shows how many workspaces/items account for 50%, 80%, and 95% of consumption, useful for prioritizing optimizations. * **Investigate an entity:** clicking a lane opens the detail with the Interactive/Background split, the breakdown, and the most expensive operations. ## Features Filters are applied automatically: when you change any of them, the KPIs, the timeline, and the cards reload. The page subtitle shows the range covered (for example, *09/01/2026 to 09/30/2026 · 30 days*). ### Capacity and period filters **What it is:** the **Period** menu, which is the first filter in the bar, and the **Capacity** selector (*All monitored* or one capacity). The **Period** menu offers **Yesterday**, **Last 7 days**, **Last 14 days**, **Last 30 days** (default), **Last 60 days**, **Last 90 days**, **Last 180 days**, and **Custom**. The menu button shows the chosen option and the date range it represents (for example, *Last 30 days: Sep 1 - Sep 30, 2026*). **What it is for:** defining the analysis window, from one week (to follow day-to-day activity) to 90 days or more (for capacity planning).

Filter bar with Period, Capacity, Workspace, Item, Clear filters, and the Export CSV and Explain with AI buttons — Consumption History filter bar

**How to use:** 1. In **Period**, open the menu and choose an option, for example **Last 90 days**. 2. In **Capacity**, keep **All monitored** or choose a specific capacity. **How it works:** each column of the timeline is a local day of the organization (time zone defined by the *UTC\_offset* parameter of the Capacity Metrics App). The current day is partial. The *Last N days* options end on the organization's current day and count it among the N days; **Yesterday** shows a single day. While the screen is loading the filter is disabled; if the first load fails, it stays available so you can change the period and try again. ### Custom period **What it is:** the **Custom** option of the **Period** menu, which displays the **From** and **To** fields. **What it is for:** analyzing a specific range, such as a month-end closing or the week of a migration.

Custom period with the From and To fields — Custom period

**How to use:** 1. In **Period**, choose **Custom**. The **From** and **To** fields appear already filled in with the displayed period. 2. Adjust the dates. The screen reloads as soon as the two dates form a valid range. **How it works:** the range can be up to 366 days, the start date cannot be after the end date, and future dates cannot be selected. Incomplete or invalid ranges do not trigger a new query. ### Workspace and item filters **What it is:** the **Workspace** selector (*All* or one workspace), the **Item** selector (*All items* or one item, with search by name), and the **Clear filters** button. **What it is for:** following the evolution of a specific workspace or item, for example a semantic model that went through optimization.

Item selector open with the Search item by name field — Item selector with search

**How to use:** 1. In **Workspace**, choose a workspace (or **All**). 2. In **Item**, click the selector (**All items**), type part of the name in **Search item by name…**, and click the item. If the list warns that it was truncated, narrow the search. 3. To return all filters to their default values, click **Clear filters**. **How it works:** filtering by item **recalculates all lanes, including the consolidated total**, to show only that item (it does not just shorten the list). The information icon next to the **Item** label is a reminder of this behavior. ### Timeline dimension **What it is:** the **Workspaces** (default), **Workloads**, and **Items** buttons, right below the filters. The number on each button is the number of entities of that dimension in the slice. **What it is for:** choosing what each lane represents: a workspace, a workload type, or an item.

Workspaces, Workloads, and Items dimension buttons with the entity count — Timeline dimension

**How to use:** 1. Click **Workspaces**, **Workloads**, or **Items**. 2. The lanes, KPIs, and cards start representing the chosen dimension. If the **Lane detail** is open, it closes. **How it works:** entities removed from the tenant appear with the suffix *(removed)*, and operations with no identified workload appear as *No identified type*. ### Period KPIs **What it is:** the row of cards right above the timeline. **What it is for:** getting the period summary (total, average, peak, active entities, and success rate) before looking at the details.

Total in period, Daily average, Daily peak, active entities, and Success rate KPIs — Period KPIs

| KPI | What it shows | | ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Total in period** | Sum of Capacity Units (s) in the period and the change *vs. the previous N days* (the immediately preceding window, of the same size). With no data in the previous window, it shows *no comparison baseline*. | | **Daily average** | Average Capacity Units (s) per day and the *low* (day with the lowest consumption). | | **Daily peak** | Day with the highest consumption and how many times it exceeds the average. | | **Active Workspaces / Workloads / Items** | How many entities of the dimension consumed in the period, *of N in scope*. | | **Success rate** | Percentage of operations completed successfully among those that recorded a status (*X of Y operations succeeded*). | **How to use:** 1. Read **Total in period** and the change against the previous window to find out whether consumption grew. 2. Compare the **Daily peak** with the **Daily average** to measure seasonality. 3. If the **Success rate** dropped, investigate in the **Lane detail** (see the frequently asked questions). ### Consumption timeline **What it is:** the main card on the screen, with the subtitle *"N of M entities · one column per day in the organization's time zone"*. It contains: * the **"Consolidated total" master lane** at the top, with its own vertical scale; * **one lane per entity** in the ranking and the **"Others (N outside the ranking)"** lane, which aggregates the rest. Entity lanes and "Others" share the same vertical scale, so their heights are comparable with one another; * in each lane, one bar per day, the highlight of the **lane peak**, and the shading of **weekends**; * next to each lane, the **Capacity Units (s) in period**, **% of total**, and **vs. previous window** columns (increase, decrease, flat, or no comparison baseline). **What it is for:** seeing trends, seasonality, and who is growing, side by side.

Consumption timeline card with the Consolidated total lane and the per-entity lanes — Consumption timeline

**How to use:** 1. Go through the lanes from top to bottom: the order follows the **Sort by** criterion. 2. Hover over the **Capacity Units (s) in period** value to see the exact number, and over the **vs. previous window** indicator to read the change in full. 3. Click an entity lane to open the [Lane detail](#lane-detail). **How it works:** the **Consolidated total** equals the sum of the displayed lanes plus the **Others** lane. With no consumption in the slice, the card shows *No entity consumed Capacity Units (s) in this slice.* ### Consumption on a day (tooltip) **What it is:** the tooltip displayed when you hover over a day's bar in any lane. **What it is for:** reading the exact value for a day and how much that entity weighed in the day's total.

Tooltip with the date, the lane value, the share of the day, and the day total — Consumption on a day

**How to use:** 1. Hover over the day's bar in any lane. 2. Read the date and the weekday, the lane value, the **share of the day**, and the **Day total**. ### Number and order of lanes **What it is:** the **Lanes** control (10, 25, 50, or 100; default 10) and the **Sort by** control (**Consumption**, default, **Variation**, or **Name**), in the header of the Consumption timeline card. **What it is for:** expanding the analysis to more entities or rearranging the lanes to find who changed the most.

Lanes and Sort by controls in the Consumption timeline card — Lanes and Sort by

**How to use:** 1. In **Lanes**, choose **10**, **25**, **50**, or **100**. 2. In **Sort by**, choose **Consumption**, **Variation**, or **Name**. 3. Entities outside the ranking remain added up in the **Others** lane. **How it works:** sorting by **Variation** uses the absolute difference in Capacity Units (s) compared with the previous window. Changing the number or the order reloads the timeline. ### Biggest movers **What it is:** the card that lists what moved the most against the previous window, in absolute Capacity Units (s), with the **Increase**, **Decrease**, or **Flat** badge. **What it is for:** quickly finding out who grew (or dropped) the most in the period.

Biggest movers card with the Increase, Decrease, and Flat badges — Biggest movers

**How to use:** 1. Set the period (for example, **Last 30 days**) and the dimension. 2. In the **Biggest movers** card, read the entities that went up or down the most compared with the previous window of the same size. 3. Click the entity's lane in the timeline to investigate in the **Lane detail**. **How it works:** the ranking is calculated over **all** entities in scope, not only over the displayed lanes. *No comparison baseline* means that the entity did not consume in the previous window, or that this window falls outside the available history. ### Consumption concentration **What it is:** the card with the Pareto curve (ranking position × cumulative share) and the **50%**, **80%**, and **95% of consumption** markers: how many entities are needed to reach each slice. **What it is for:** prioritizing optimizations on the few entities that account for most of the consumption.

Consumption concentration card with the Pareto curve and the 50, 80, and 95 percent markers — Consumption concentration

**How to use:** 1. Read how many entities account for **50%**, **80%**, and **95% of consumption**. 2. Prioritize optimizations on the entities that make up the first 80%. **How it works:** the curve is calculated over all entities in scope, never over the displayed top N. *Not reached* means that the tail outside the ranking still accounts for the rest (it is not zero). ### Lane detail **What it is:** the side panel opened when you click an entity lane, with the lane KPIs: Lane Capacity Units (s) (with the previous window value), change, **% of total**, daily average, and daily peak. **What it is for:** investigating a specific entity without leaving the timeline.

Lane detail panel with KPIs, usage type split, and most expensive operations — Lane detail

**How to use:** 1. In the timeline, click the entity's lane (workspace, workload, or item). The **Lane detail** panel opens. 2. Check the consumption in the period, the change, the **% of total**, the daily average, and the daily peak. 3. To close it, click the panel's **X**, click outside it, or press **Esc**. **How it works:** the **% of total** is measured against the scope total, not against the lane itself: it is the same number as the *% of total* column in the timeline. The **Consolidated total** and **Others** lanes do not open a detail. ### Daily consumption and usage type **What it is:** the Lane detail chart in which each column is a day, split into **Background**, **Interactive**, and **Unclassified**, with the period totals. **What it is for:** knowing whether the entity's consumption comes from automated routines or from people using reports, and on which days.

Daily consumption and usage type chart with Background, Interactive, and Unclassified — Daily consumption and usage type

**How to use:** 1. Open the Lane detail. 2. Compare the colors in each column and the **Period totals** for **Background**, **Interactive**, and **Unclassified**. **How it works:** Background + Interactive + Unclassified = day total. **Unclassified** groups the operations that arrived from the Capacity Metrics App with no utilization type; they count toward the total, which is why they appear in the chart. ### Lane breakdown **What it is:** the **Breakdown by** section of the Lane detail, which shows how the lane is split by the other dimension (for example, the items of a workspace). **What it is for:** finding, within a workspace or workload, which item concentrates the consumption.

Breakdown by dimension section in the Lane detail — Lane breakdown

**How to use:** 1. Open the Lane detail and scroll to **Breakdown by** . 2. Read the largest shares. **How it works:** the share is measured against the lane itself (unlike the % of total in the KPIs). The dimensions displayed depend on the lane clicked. ### Most expensive operations **What it is:** the Lane detail table with the **Operation**, **Capacity Units (s)**, **Executions**, **Success rate**, and **Average duration** columns. **What it is for:** identifying which of the entity's operation types cost the most and whether they are failing.

Most expensive operations table with Operation, Capacity Units, Executions, Success rate, and Average duration — Most expensive operations

**How to use:** 1. Open the Lane detail and scroll to **Most expensive operations**. 2. Read the first rows: they are the operations with the highest consumption in the period. 3. Check the **Success rate** and the **Average duration**. To see each execution, use [Consumption Metrics](/en/power-monitor/monitoramento/metricas-de-consumo.md). **How it works:** the table is sorted by Capacity Units (s) over all of the lane's operations in the period. When no execution recorded a status, the rate is not calculated (it is not 0%). ### Export CSV **What it is:** the **Export CSV** button, on the right of the filter bar. **What it is for:** taking the slice to a spreadsheet, for example for a monthly FinOps report.

Export CSV and Explain with AI buttons — Export CSV and Explain with AI

**How to use:** 1. Leave the desired dimension, period, filters, number of lanes, and sort order on screen. 2. Click **Export CSV**. **How it works:** the file reproduces exactly the slice displayed, with the entity columns (name and key), Capacity Units (s) in period, % of total, Previous window (Capacity Units (s)), Change (%), and one column per day (dates in YYYY-MM-DD format). The button is disabled when there is no consumption in the slice. The file contains names of workspaces and items in your environment: share it with care. ### Explain with AI **What it is:** the **Explain with AI** button, which sends the numbers of the displayed slice to the AI configured in *Settings › AI* and opens the **Consumption history analysis** modal. **What it is for:** getting a text that summarizes the trend, the concentration, and what drove consumption, useful as a starting point for a presentation.

AI-generated Consumption history analysis modal — Explain with AI

**How to use** (prerequisite: AI provider configured and spending limit available in *Settings › AI*): 1. Build the slice you want to analyze (period, dimension, and filters). 2. Click **Explain with AI**. The modal opens and displays *Analyzing the consumption of the slice on screen…* while the response is generated. 3. Read the analysis. The text is AI-generated: review it before acting. **How it works:** the analysis consumes the organization's AI quota. The button is disabled when there is no consumption in the slice. ## Rules and behavior * **Daily granularity:** each column is a local day of the organization (time zone defined by the *UTC\_offset* parameter of the Capacity Metrics App). * **Data source:** per-item operations collected from the Microsoft Fabric Capacity Metrics App every 5 minutes; the current day is partial. * **Previous window:** comparisons use the immediately preceding period with the same number of days. * **Partial history:** if the period starts before the first day with data, the **"Partial history"** warning appears: days before Power Monitor was adopted do not exist, lanes start where the data starts, and comparisons with windows before that date appear as "—". * **No monitored capacity:** the screen shows **"No monitored capacity"** and hides the filters. Administrators see the **Configure capacity monitoring** button; other users are advised to contact an administrator. * **Capacity Metrics App not found:** if the metrics source does not exist, the screen explains that there is no source for the numbers (this is not a loading failure, and retrying does not solve it). See [Enable Capacity Monitoring](/en/power-monitor/monitoramento/capacidades/ativar-monitoramento-de-capacidade.md). * **Loading failure:** if the query fails, the screen shows **Could not load the consumption history** with the **Try again** button; shortening the queried period can also help. * **Explain with AI** consumes the organization's AI quota and depends on a provider configured in *Settings › AI*. ## Frequently asked questions

The sum of the entity lanes does not match the Consolidated total.

The displayed lanes are only the top N chosen in **Lanes**; the rest is in **Others**. Consolidated total = displayed lanes + Others.

The Success rate dropped in a period. How do I find the failures?

Open the **Lane detail** of the entities with the highest consumption and look at the **Success rate** column in *Most expensive operations*. To see each execution, use [Consumption Metrics](/en/power-monitor/monitoramento/metricas-de-consumo.md), filtering by the day and by **Status** *Failed*.

Why does "no comparison baseline" appear?

The entity did not consume in the previous window, or that window falls outside the available history.

## Related pages * [Consumption Comparison](/en/power-monitor/monitoramento/comparativo-de-consumo.md) * [Consumption Metrics](/en/power-monitor/monitoramento/metricas-de-consumo.md) * [Consumption Anomalies](/en/power-monitor/monitoramento/anomalias-de-consumo.md) * [Capacities (Capacity Monitoring)](/en/power-monitor/monitoramento/capacidades.md) * [Capacity Dashboard](/en/power-monitor/dashboards/dashboard-de-capacidade.md) * [Capacities (menu)](/en/power-monitor/capacidades.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://docs.powermonitor.com.br/en/power-monitor/monitoramento/historico-de-consumo.md?ask=&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.