Advisor
NeophyteIf I understand correctly, this Collector setting for VMs controls how those VMs get monitored as Devices after discovery.
When the LM Azure integration finds new cloud VMs, some data about them is gathered via the Azure API like you mention. But then that VM can also be monitored like any other Device within your system - just like an on-premisies server, for example.
So that Collector setting controls the handoff from the Azure-monitoring to the Collector-monitoring of the VM. The default assigned Collector can then takeover and run things like WMI queries, ping tests, etc to gather data from outside of Azure.
AdvisorThat's correct. What I'm asking for here is a way to do the same but for cloud resources that are not Virtual Machines. This would allow us to use custom modules to pull data from the Azure APIs, without having to manually assign a collector group to those other resources.
