You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How (and where) can I edit, add, or remove Blades in the monitoring view ? The monitoring view for example assumes that I have the use for a "IN CLUSTER SECURITY" blade. I don't have any clusters and I want to delete this blade. When loading the interface it also throws errors that I believe are related to not having collected any data for the blade ("Request is invalid and cannot be executed.\",\"innererror\":{\"code\":\"SEM0100\",\"message\":\"'summarize' operator: Failed to resolve table or column expression named 'AzSKInCluster_CL'\",\)
How can I edit or remove a azSkViewName ? The documentation tells me how to SET this name while running the Install-AzSKMonitoringSolution - but how do I modify or delete it ?
I find this whole view frustrating to use, I want to make a few relevant queries and then display them in a dashboard
Thank you
The text was updated successfully, but these errors were encountered:
Hi guys
How (and where) can I edit, add, or remove Blades in the monitoring view ? The monitoring view for example assumes that I have the use for a "IN CLUSTER SECURITY" blade. I don't have any clusters and I want to delete this blade. When loading the interface it also throws errors that I believe are related to not having collected any data for the blade (
"Request is invalid and cannot be executed.\",\"innererror\":{\"code\":\"SEM0100\",\"message\":\"'summarize' operator: Failed to resolve table or column expression named 'AzSKInCluster_CL'\",\
)How can I edit or remove a azSkViewName ? The documentation tells me how to SET this name while running the Install-AzSKMonitoringSolution - but how do I modify or delete it ?
I find this whole view frustrating to use, I want to make a few relevant queries and then display them in a dashboard
Thank you
The text was updated successfully, but these errors were encountered: