Forum Discussion

Dave_Lee's avatar
Dave_Lee
Icon for Advisor rankAdvisor
22 days ago

Collector Monitoring of Azure Resources

There are various issues and omissions with LogicMonitor's default Azure monitoring datasources.

We have ended up having to write custom modules for a number of things to make sure that we have sufficient coverage.

The issue with this is that LM doesn't use Collectors to monitor cloud resources.  These datasources seem to run on the platform itself.  We cannot change the built-in modules - understandably as I guess these run on the LM platform, not a collector, so they don't want us running potentially damaging code.

For Virtual Machines, there is an option in the UI to set a collector to be used for monitoring.  Once you set this up, all VMs that match the criteria you give will be monitored by a collector.


This is not available for other resources - no longer resource/service types have the Collector tab.


For example, I have custom data sources for Azure Virtual Desktop that pull information from the Azure API that LogicMonitor's default modules do not cover.  I can make this work if I set a collector group individually on each of the Virtual Desktop host pools.  This is quite manual and needs to be done individually for each resource.

 

Please could you allow us to set a default collector group to be used for all cloud resource types, not just Virtual Machines.

2 Replies

  • jhupka's avatar
    jhupka
    Icon for Neophyte rankNeophyte
    21 days ago

    If 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.

    • Dave_Lee's avatar
      Dave_Lee
      Icon for Advisor rankAdvisor
      21 days ago

      That'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.