Collection Status¶
Where to check that each Power BI environment, and each of its collectors, is current.
How it works¶
Collection has two layers (see Collection Schedule): collectors that call Microsoft and write to the MetaMiner Database (MMDB), and a 10-minute snapshot cycle that publishes the collected data to the MetaMiner Client (MMC). Each place below shows one layer.
| Where | Shows | Layer | Who can see it |
|---|---|---|---|
| MMC Notification Center, Freshness tab | Per environment: state, last success, last run | Snapshot cycle | MMC users |
server\logs\statereport.log |
Per environment and per collector: current state, last result, error count | Collectors | Administrators on the server |
| MMA health indicator | Server-wide issues from the logs | Whole server | Administrators on the server |
| Analyze Logs report | Freshness and pull status per environment, from the logs | Snapshot cycle | Administrators |
| Usage dashboards | Data state of each dashboard domain | Dashboard rollups | Dashboard users |
Check in the MetaMiner Client¶
- In MMC, click the status indicator in the status bar. It reads "N urgent", "N notable" or "no issues".
- The Notification Center opens. Select the Freshness tab.
- Find the PBI section. Each row is one environment.
| Column | Meaning |
|---|---|
| Environment | Environment display name |
| State | OK, RUNNING, STALE or ERROR |
| Last success | When the last snapshot cycle completed |
| Last run | When the last snapshot cycle started |
| Cycle, Reachable, Note | Additional detail from the server |
The tab refreshes every 30 seconds. When the server cannot report freshness, the tab shows "health unknown" rather than a green state.
Image of the MMC Notification Center, Freshness tab, with the PBI section showing one environment in state OK
../../images/admin/mmc-freshness-pbi.png
OK means the snapshot is current
For Power BI the row tracks the snapshot cycle, which reads the MMDB. A collector that has stopped receiving data from Microsoft (for example after a revoked permission) does not turn this row red. Check the state report for collector-level status.
Check each collector in the state report¶
MMS writes a state report to server\logs\statereport.log every 60 minutes.
- Open
server\logs\statereport.log(File > Open Log Folder in MMA). - Search from the end of the file for "Configured Power BI Environments", the start of the Power BI part of the latest report.
- Under it, find the environment ID: each line shows the ID,
+for enabled or-for disabled, and the name. - Under "Power BI Workers", read one line per collector (for example
ACTIVITY_EVENTS,WORKSPACE_SCAN,FCM): the result of its last step, its current state and its error count.
| What you see | Meaning |
|---|---|
| Errors: 0 | The collector is working |
| Errors above 0 | The last steps failed; the collector retries with increasing waits (1 second up to 5 minutes) |
| A long wait after a 429 | Microsoft throttled the collector; it resumes on its own |
| DISABLED | The collector was turned off with its processor.enabled property; see Collection Schedule |
The full error of a failing collector is in server.log around the same time. Include both files in a log bundle when you contact Infolytik Support.
Check from MMA¶
- The Server Health Indicator turns amber or red when the logs show notable or urgent issues, including repeated collection errors.
- File > Analyze Logs... produces a report with a Substrate freshness & pull status table per environment; see Analyze Logs.
- Status in BI Environments shows the last validation result, not collection progress.
Check the dashboards¶
Each usage dashboard shows the state of its data, for example backfilling or stale, and when its rollups last ran. See Data Freshness.