Forum Discussion

Dave_Lee's avatar
Dave_Lee
Icon for Neophyte rankNeophyte
8 months ago
Solved

Excluding VMware VMs from instance discovery

When we add a vCenter into Logic Monitor, the VMs in it’s managed clusters are discovered as instances of underneath datasources applied to the vCenter, like: VMware VM Status VMware VM Snapshots ...
active discovery
tagging
vmware
  • Dave_Lee's avatar
    Dave_Lee
    8 months ago

    Thanks @tswisdom - I think Active Discovery Filters is just what I’m looking for here.  Looking through the Active Discovery script for the VMware_vCenter_VMStatus datasource, it look as though that should be returning tags in it’s output, but doesn’t seem to be doing so.  I’ll have to dig a little deeper into that, then look at the Active Discovery Filters.

    thanks

    Dave

tswisdom's avatar
tswisdom
Icon for LM Champion rankLM Champion
8 months ago

Good afternoon @Dave Lee,

While our enhanced netscan script for adding VMWare resources allows you to leverage several filters to exclude VM’s and other components, the datasources for various VMWare resources do not currently include native filtering.

With that said, there are two approaches you could take to automate how instances are handled.

The first would be as you suggested, modifying the Active Discovery script to pull tags or other items you wish to key off of, then configuring Active Discovery Filters to exclude instances based off of the data.

Alternatively, you can configure your alert rules to only match, or exclude, particular instances for these modules, routing some but not others.