- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Data activator in Fabric capacity metrics app not working
Hi - I have been trying to set up alerts for the fabric capacity metrics app. I have set the workspace to premium capacity and I am the admin of the workspace. Still when I am trying to set an alert for the utilisation graph or throttling graph to get an alert when total CU usage % is greater than 100%, I receive this error:
I have tried the workaround mentioned in Build Alerts for Fabric Capacity Metrics App using Data Activator | Microsoft Fabric Admin - YouTube - but also receieved the same error message.
Anyone who have had any success to set up alerts in the Fabric capcity metric report or who can help me avioding this error?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @EmiliaT ,
According to the documentation, fabric capacity metrics need to be in the fabric workspace. Please select the fabric capacity metrics app and click Workspace Settings to change the license info.
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@v-tangjie-msft I changed the workspace setting and put in in a fabric capacity setting - still receives the same error message. What else could be done to aviod it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @EmiliaT ,
According to the documentation, fabric capacity metrics need to be in the fabric workspace. Please select the fabric capacity metrics app and click Workspace Settings to change the license info.
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had already challenged Microsoft on that. It is one of the basic tenets of monitoring that the monitor should never be placed in the system it monitors. The requirement stated in the documentation is in blatant violation of that basic tenet.

Helpful resources
Join us at the Microsoft Fabric Community Conference
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Fabric Monthly Update - February 2025
Check out the February 2025 Fabric update to learn about new features.

Subject | Author | Posted | |
---|---|---|---|
01-28-2025 11:23 AM | |||
11-28-2024 08:54 AM | |||
07-11-2024 05:48 AM | |||
04-05-2024 01:25 AM | |||
06-28-2024 02:09 AM |