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
About "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...Jarrinf1 hour agoFrequent VisitorNew47Views3likes2CommentsEventstream MQTT broker source: V3.1.1 support
The Eventstream MQTT broker source supports connections with public MQTT brokers that offer MQTT V5 support. Please offer support for V3.1.1 too, because this is still a valid and widely used ver...svelde3 hours agoSuper UserCompleted1.4KViews6likes4CommentsGet data from Apache Kafka topics via private networking
Current prerequisites limit to public Kafka instances which is not feasible for most enterprise customers. When will this limitation be lifted so that it can be used in private network setups, for ...Jugi3 hours agoMicrosoft EmployeePlanned3.5KViews2likes3CommentsSet default x axis scrolling position
Enable selection of the default scroll position for the x-axis on a chart. For example, on a line chart with dates as the x-axis, when not all of the data can display in the view at once, the scroll...Lisa_Krieg11 hours agoNew MemberNeeds Votes7.8KViews1154likes104Comments