Today, Workspace Monitoring is configured separately per workspace, which introduces maintenance overhead and likely also a repeated baseline CU cost for each workspace.
Please make it possible to create Workspace Monitoring instances that cover multiple workspaces.
Users should be able to decide how many monitoring instances to configure and which workspaces each instance covers.
This would allow the baseline monitoring cost to be shared rather than incurred separately per workspace, reducing overall cost while also simplifying configuration and ongoing maintenance. In addition, it would enable a more centralized and flexible monitoring setup across workspaces.
No CommentsBe the first to comment
Recent ideas
Semantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v2 hours agoCommunity ChampionNew10Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal1401976 hours agoFrequent VisitorNew5Views0likes0CommentsAbout "Download SQL database project" and fix the downloaded project
1. The sqlproj must be fixed, it is downloaded without the xml markup line <?xml version="1.0" encoding="utf-8"> 2. The sdk must be updated: Actual: <Sdk Name="Microsoft.Build.Sql" Version="0.1...Jarrinf16 hours agoFrequent VisitorNew48Views3likes2Comments