Daily collection and history

Once a day — overnight by default — PBI analyzer reads what the Fabric Capacity Metrics app currently shows for each of your capacities, and saves it. The Capacity page of the Admin Console shows when the last collection ran and when the next one is due, and Collect now runs one on demand.

Each run collects the daily CU totals, the split between interactive and background use, and — where Fabric publishes it — the per-item detail.

Why the analyzer keeps its own copy

Microsoft keeps only a rolling window. The Capacity Metrics app holds the last 30 days and discards everything older; the per-item detail goes back about two weeks.

Soterre PBI Analyzer keeps up to 90 days and shows 30 by default.

An interruption has a deadline

If collection stops — the server is down, the service is off, a client secret expired — the next successful run repairs the gap by itself. It checks the last day it saved and asks for everything since.

That repair reaches back 30 days, because 30 days is all Fabric can still answer for.

Worked example

Collection stops on 1 March. Nobody notices until 15 April, 45 days later.

The run on 15 April reaches back to 16 March and refills those days. 1–15 March are gone permanently.

What this means for you: notice an interruption within a month and you lose nothing.