Skip to content

Capacity Metrics App

Install the Microsoft Fabric Capacity Metrics app, give MetaMiner read access to its semantic model, and point MetaMiner at it to collect capacity utilization.

How it works

Microsoft publishes capacity utilization (capacity units, throttling, storage, per-item operations) through the Microsoft Fabric Capacity Metrics app, not through an admin API. MetaMiner reads it by running read-only DAX queries against the app's semantic model every 60 minutes. The data feeds the Capacity Metrics dashboard and is kept for 26 weeks by default.

This part is optional. Without it, MetaMiner still collects capacities and everything else. Unlike the rest of the collection, it needs a workspace role.

Collected from the Capacity Metrics model First collection reads
Capacities Current list
Items Last 24 hours, then hourly
Compute by item and operation per hour Hour by hour, from 14 days back
Capacity unit (CU) detail From 14 days back
Storage by workspace per hour From 14 days back

Before you begin

  • A capacity admin who can install the Capacity Metrics app and connect it to your capacities.
  • A Fabric administrator for the tenant settings.
  • The MetaMiner service principal and its security group. See Security Group for the App.

Steps

Install the app and give MetaMiner access

  1. Install the Microsoft Fabric Capacity Metrics app and connect it to your capacities, following Microsoft's instructions. Keep the app current.

    TODO: link and re-check Microsoft's installation steps for the Capacity Metrics app

    Source to check: Microsoft Learn, "Install the Microsoft Fabric Capacity Metrics app". Note the current app name and where it is installed from (Fabric portal Apps or AppSource).

  2. Refresh the app's semantic model once so that it holds capacity data.

  3. Open the workspace that holds the app and give the MetaMiner service principal, or its security group, the Contributor or Admin role. See Workspace Access.
  4. In the Fabric admin portal, enable for the MetaMiner security group: Semantic model Execute Queries REST API (Integration settings) and Allow service principals to use Power BI APIs. See Tenant Settings.
  5. Find the semantic model ID: open the app's semantic model in the Power BI service and copy the ID from the browser address after /datasets/.

    TODO: re-check where the semantic model ID is shown in the current Power BI service UI

    The ID is a GUID such as 0a34b44b-79c9-40c0-ac1e-fab7dc059a9b.

Image of the Capacity Metrics semantic model page in the Power BI service with the dataset ID visible in the address bar

../images/microsoft-setup/fcm-semantic-model-id.png

Point MetaMiner at the semantic model

  1. In the MetaMiner Administrator, edit the Power BI environment.
  2. Clear Ignore FCM at this time.
  3. Under FCM Datasets & Capacities, click Add and enter the semantic model ID.
  4. Click Load Capacities and select the capacities you want to track.
  5. Click Test Connection, check that Fabric Capacity Metrics Data passes, and click Apply.
  6. Restart the MetaMiner Server.

Details: Capacity Metrics Datasets.

Image of the FCM Datasets & Capacities area with one semantic model ID and two capacities checked

../images/microsoft-setup/mma-fcm-datasets-capacities.png

Which capacities are collected

  • Paid F and P capacities are included.
  • Trial capacities are excluded automatically.
  • The legacy embedded SKUs EM1-EM3 and A1-A3 are not offered in the capacity list.
  • If you select no capacity at all, MetaMiner collects all capacities. To turn Capacity Metrics off, select Ignore FCM at this time instead.
  • A capacity that was removed from the tenant is skipped, and collection continues with the others.

Verify

  • Test Connection shows Fabric Capacity Metrics Data <semantic model ID> as passed.
  • After the next collection cycles, the Capacity Metrics dashboard shows utilization.

Troubleshooting

Fabric Capacity Metrics Data fails with Validation failed

The service principal is not Contributor or Admin on the app's workspace, one of the two tenant settings is off for its group, or the ID is wrong. Fix the workspace role and settings and test again.

Validation was green before and now fails

Updating or reinstalling the Capacity Metrics app creates a new semantic model with a new ID. Replace the old ID with the current one.

Unsupported Capacities column layout

The installed app version uses a table layout this MetaMiner release does not understand. MetaMiner supports the two layouts whose capacity ID column is Capacities[capacityId] or Capacities[Capacity Id]. Check the app version, or select Ignore FCM at this time until a MetaMiner release supports it.

No capacities returned

The app's Capacities table is empty. Refresh the app and check that it is connected to at least one capacity the service principal can see.

Validation skipped: No FCM configured

No semantic model ID is entered and Ignore FCM at this time is cleared. Enter an ID, or select Ignore FCM at this time. Test Connection treats this step as failed until you do one of the two.

Next steps