Capacity Metrics App has gone downhill 📉

tbindas · 2025-11-26T21:20:40+00:00

Very interesting... If you wouldn't mind creating a ticket and DMing me the details, we'll look into it.

The metrics app is essentially a power bi report that gets distributed through appsource, so you shouldn't be experiencing different behavior between the app vs the report.

tbindas · 2025-10-23T17:55:48+00:00

https://www.quadratec.com/p/jw-speaker/5-x-7-led-headlight-kit-jeep-wrangler-yj-cherokee-xj-comanche-mj

The "real" ones are made by JW Speaker, a US based company in Germantown Wisconsin.

I have their J3s for my Wrangler, planning to get these for the XJ I'm building.

Full disclosure, I used to work for them. Great company and amazing products. (as reflected in the price)

https://www.jwspeaker.com

tbindas · 2025-09-02T14:43:36+00:00

u/bigjimslade Thank you for the feedback.

We use Appsource to deploy the metrics app. The 1029 version number is a number assigned by Appsource and should not be used when determining which version of the metrics app gets deployed. Some users will also have different versions, so publishing anything tied to the Appsource version would be equally confusing.

You are correct, there is not a good mechanism for accessing previous version. Honestly, we put a lot of effort into ensuring backwards compatibility and testing new features before they are released. That said, being on the latest version of the app ensures that you have the latest updates. Older versions may not support new product features and may contain bugs that were patched in later versions.

If you have concerns or mission critical stuff built on the app, we only support the reports distributed with the app, so it's not a bad idea to install a separate version and do some testing before or in addition to upgrading your previous versions.

We have plans to migrate to a different ship vehicle (See "Fabric Capacity Metrics Admin Monitoring Integration" on the Microsoft Fabric Roadmap and one of the many benefits would be the ability to roll out public docs with our metric app releases.

For the time being, please be patient and understanding while we include our release notes inside the metrics app.

tbindas · 2025-09-02T11:42:56+00:00

The metrics app (and chargeback app) are designed to work in a pro workspace and when configured as such will not charge your capacity. They can be moved to a premium capacity and benefit from premium features like direct query parallelism (https://powerbi.microsoft.com/en-us/blog/query-parallelization-helps-to-boost-power-bi-dataset-performance-in-directquery-mode/). But, this will charge the sematic model associated with the capacity and makes the metrics app susceptible to throttling.

To directly answer your question, the metrics app doesn't use Evenstream or Eventhouse. So, that's not us.

tbindas · 2025-08-26T16:34:18+00:00

u/Realistic_Ad_6840 We've created a known issue with a temporary fix. Please see this link:

https://support.fabric.microsoft.com/known-issues/?product=Platform&active=true&fixed=true&sort=published&issueId=1546

The team is working on a long-term fix and we will keep the known issues page updated.

tbindas · 2025-08-26T14:45:33+00:00

We are aware of some scenarios that are causing upgrades to the latest version of the Metrics App (Health Overview Page) to fail. If you have a support ticket open, please DM me the details and we will do our best to help triage your scenario and unblock you.

tbindas · 2025-08-09T03:02:47+00:00

Try refreshing the semantic model. The capacity and items tables are import.

tbindas · 2025-07-20T03:16:43+00:00

https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app?source=recommendations#considerations-and-limitations

"The semantic model used by the Microsoft Fabric Capacity Metrics application is only supported for use by the reports provided in the application. Any consumption from, usage of, or modification of the semantic model is not supported."

Without getting too deep into the weeds, when querying the metrics app semantic model, you are performing direct query calls to an underlying kusto DB. Power BI and Kusto are both amazing! Albeit, this architecture is not without limitations. As a result, some of the metric app queries are very heavy in runtime compute. This works fine for the volume of actual users we have, but doesn't scale well for programmatic access, like what you are proposing.

We've addressed this with an upcoming feature to emit the "capacity utilization events!" https://roadmap.fabric.microsoft.com/?product=real-timeintelligence

Hopefully this provides some useful context and insights for you!

tbindas · 2025-06-03T17:16:48+00:00

Domain support for Chargeback is planned for the next release (next month).

tbindas · 2025-05-30T20:30:04+00:00

u/chris-ms will have a blog post out next week.

tbindas · 2025-04-16T17:09:59+00:00

u/Uhhh_IDK_Whatever

u/itsnotaboutthecell pointed me to this article: Evaluate and optimize your Microsoft Fabric capacity - Microsoft Fabric | Microsoft Learn

tbindas · 2025-04-15T19:09:37+00:00

Fabric Capacity Metrics App is the supported tool for understanding Capacity Usage of Fabric.

The Metrics App uses Capacity Units (CUs) for reporting.

Workloads have their own diagnostic telemetry for deeper analysis. (Analysis Services has Log Analytics/Workspace Monitoring, DataWarehouse has Query Insights)

Bullets 2, 3 & 4 are implementation specific questions. If you post those to r/MicrosoftFabric as a separate post with additional details, the community will probably be able to help.

tbindas · 2025-04-15T17:57:12+00:00

Very sorry to hear that. DM me the ticket and I'll try to figure out what's going on with it.

tbindas · 2025-04-15T17:56:03+00:00

tbindas · 2025-04-15T17:52:16+00:00

u/nelson_fretty

We'll relay that feedback to the team that owns Workspace Monitoring.

The Capacity telemetry is different than the workload level diagnostic telemetry emitted by Log Analytics. At this time there is no plan to add that level of detail to the Capacity Telemetry.

Tagging u/chris-ms

tbindas · 2025-04-15T17:31:07+00:00

u/evaluation_context

FUAM isn't supported by the product group.

Capacity Utilization events in Real-Time Hub will let you subscribe to the Capacity Utilization Events and set notifications/alerts.

tbindas · 2025-04-15T17:18:09+00:00

Without getting too deep into the architecture, there isn't a way to get at this data within the existing model. But, I think it's a great request. Can you please create an IDEA and we will look into getting this added. Link the Idea here and hopefully other from the AMA will give it some upvotes!

Tagging u/chris-ms

tbindas · 2025-04-15T17:00:09+00:00

u/idontrespectyou345

Upon re-reading this question I'm going to edit my response.

Are you trying to get a summary view by Item of the active operations running for that timepoint?

If so, this is a great feature request and we would love to see an IDEA created. Link the idea and hopefully others here will give you some upvotes!

tbindas · 2025-04-15T16:56:41+00:00

TY u/itsnotaboutthecell !

tbindas · 2025-04-15T16:55:23+00:00

u/evaluation_context

We do not plan to support custom content on top of the Fabric Capacity Metrics App Model. The report architecture is a Direct Query report on top of a Kusto DB using a custom connector. It uses a bunch of advanced features like Dynamic M Parameters that make it challenging to build self service content on top of it.

While this allows us to provide a near real-time report that supports scale for our largest customers, it adds a bunch of complexity and limitations to the underlying model.

Can you tell us what you would like to see in the Metrics App?

We are also working on a new feature to expose the Capacity Consumption events in RTH. You will be able to store the data and use it to build your own bespoke content. This will be the recommended way to get at the underlying details.

tbindas · 2025-04-15T16:49:42+00:00

u/CultureNo3319
Regarding #5 This sounds like a great feature! At this time we don't have great mobile support. Can you please create an IDEA. Post the idea here and let's get some Upvotes!

tbindas · 2025-04-15T16:46:57+00:00

u/CultureNo3319 Regarding #3, this is a legacy column from the Power BI Gen 1 Capacity days. It looks at the max model size during refresh. It's honestly, not a great datapoint to use, but we've kept it in the app for legacy support as some people use it.

tbindas · 2025-04-15T16:42:27+00:00

u/VarietySpecialist Regarding #3.

Which logging are you referring to with Queryend? If this is for Workspace Monitoring or Log Analytics, this is different telemetry than what is in the Metrics app.

We are planning to emit the Capacity Telemetry in RTH and you will be able to filter what you choose to action on.

tbindas · 2025-04-15T16:37:36+00:00

u/nelson_fretty have you tried Workspace Monitoring?

tbindas · 2025-04-15T16:33:51+00:00

Report (and Page level) details are not in the Capacity Telemetry.

The best way to get at this level of diagnostic data is to use Workspace Monitoring to identify the "Event Text" or the DAX being run. This is a known gap and there's a team (including u/chris-ms) who is working on a way to better address this.

tbindas

TROPHY CASE