Agentless objects representing virtual cluster servers should ideally be situated under the node that currently hosts them
Agentless objects under “Administration\Device Management\Agentless Managed” representing virtual cluster servers should ideally be situated under the node that currently hosts them.
As it stands, the objects reside under the cluster node that they were first discovered on. This is highly confusing for the user.
This is a great idea but Kevin H mentioned that this might result in config churn so how do we get around that? What would we do if this were being monitored with Azure Monitor? Could a similar approach be taken?