How to Cancel Interactive operations from Fabric capacity metric

[stellahe102]

Hi,

Our team owns a capacity within the company, and it occasionally reached the capacity limit due to user not following the best practices in querying or creating new reports,  and the all the workspaces in that capacity are taken down or super slow. These are mostly from interactive (vs scheduled) operations, we are trying to proactively catch these such behaviros and cancel them, so the question is - can we actually cancel or kill an interactive job from capacity admin perspective? and how can we get alerted in the earliest possible time?

[v-nmadadi-msft]

Hi @stellahe102,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[andrewsommer]

You can but how depends on the specific workload that you are running. 

For SQL queries you need to go to SQL Endpoint Monitoring and Cancel the query. 

For Pipelines find them in the monitoring tab and then select Cancel Run

Notebooks, click stop-session in the top right corner

For a runaway query on a PBI report I don’t think there is much you can do.

To avoid this we always recommend really limiting down who can create things.  From my experience many organizations have struggled with how to realign human effort in the new data world we live in.  It used to be a space where it was common to through a lot of bodies at the problem because of the immaturity of the tools and lack of automation.  However, this space has developed and matured so much over the past decade and has become a very specialized skill set.