Workspace Monitoring

[animeshdada]

Hi,

I'm the Fabric Capacity admin and was trying to enable workspace monitoring for one of the workspaces I created for my team. The capacity is in Australia East and when I try to click the button to add a monitoring eventhouse, it throws this error (removed the IDs at the top) immediately. Is there any step missing prior?

Activity ID: ---------------------------
Request ID: ----------------------------
Correlation ID: --------------------------
Status code: 400
Time: Thu Jan 16 2025 15:42:26 GMT+1000 (Australian Eastern Standard Time)
Service version: 13.0.24852.33
Client version: 2412.1.22075-train
Cluster URI: https://wabi-australia-southeast-redirect.analysis.windows.net/

[v-menakakota]

Hi @animeshdada ,

Thank you for reaching out to us on the Microsoft Fabric Community Forum.

If log analytics is already enabled for the workspace, you must first delete the existing log analytics configuration and wait for a few hours before enabling workspace monitoring again.

Go through the below link documentation :
Workspace monitoring overview - Microsoft Fabric | Microsoft Learn


If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

[animeshdada]

I tried removing log analytics, waited for 2 days. The issue persists. Raised a ticket with Microsoft and there's no resolution yet. Will keep this group posted.

[v-menakakota]

Hi @animeshdada ,

Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.

[animeshdada · Accepted solution]

It's resolved now. So, the suggestion I received from the support team is, when I add the EventHouse, not to move away from that page. So, first, I tried to do this for a brand new workspace and then, for the original WS, as I already removed LogAnalytics from there. Both worked. 

[v-menakakota]

Hi @animeshdada ,

I'm happy to hear that your issue has been resolved. Please mark your answer as the accepted solution so Community Members can easily find it.

Thank you and regards,
Menaka.