Allow me to remove managed systems (Management Groups and Directly Connected Servers/Agents) from Usage page
Implements a feature to remove managed （ Management Groups and to Directly Connected Servers ） Overview Usage from want? I think even if servers Connected Directly, the agent is uninstalled, cannot be removed from Operational Insights Usage. Cannot disconnect in the SCOM Management Groups are for the Operational Insights on want to remove.
In the current implementation, Management groups CAN already be removed, but only once they are ‘stale’ == have not reported ANY data for >14days, the link to remove will appear.
The number of Directly reporting agents in ‘settings’ page is the actual number of servers registered, but the drill down will take you to search (where servers presence is inferred from the data).
We will be working on options to de-register directly connected servers, similarly to we offer for SCOM management groups.
Yes, *eventually* - as the retention period is elapsed. Not because you removed it. We only groom based on the TIME and your data plan.
Wei Li commented
At least making sense to me now:
I was only talking about servers connected through OI within OpsMgr when I created the post. If I delete a server from Operational Console, all data will get groomed out eventually as OpsMgr stops sending data over for that server. Once that happens, the server will no longer show under "Connected Sources" or any search.
Wei Li commented
Removing servers from Operational Insights in OpsMgr does not remove server from under "connected sources".
Norio Sashizaki commented
Thank you, I understand.
For Management Groups, see this older thread http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519336-how-to-remove-a-management-group-from-advisor
We also need to provide a means to UN-authorize/disconnect agents (like you can REMOVE now not reporting SCOM management groups).
Deletion of DATA is NOT a goal, anyhow.
Our ‘big data’ architecture doesn’t make it easy to delete things selectively. Eventually data will stale out and be groomed based on the retention period.
We do need to provide a mean do de-authorize and ‘force disconnect’ agents, anyhow.
There are some more info about this topic in this other thread (I think I will later merge this with it as they are essentially the same ask) http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519218-purging-non-reporting-servers and read the comment thread as it contains information about how to get this info from search.
Also, in 'Servers and Usage' page, now those tiles for direct agents count are based off search data. If machines simply 'go away' and it was intentional (i.e. scale back, removed the server, whatever), they'll also 'fall off' the count on the tile after data is not seen from them in 14 days. Everything is currently seen in terms of 'data flow'.