Forum Discussion

mtate's avatar
mtate
Icon for Contributor II rankContributor II
3 months ago
Solved

Filter out VMware Virtual Machines from being monitored in SL1

We have approximately 300 virtual desktop VMware Virtual Machines that we do not want to monitor via the VMware Vcenter PowerPack in SL1. All other Virtual Machines and Virtual Hosts will be monitored as normal.

Is there anyway of filtering/suppressing/vanishing these devices so we do not monitor them and they do not get counted in our licence count ?

  • gtrietsc's avatar
    gtrietsc
    3 months ago

    What we have done is not grant permissions to the SL1 account to view the objects in vCenter.  So instead of seeding the permissions at the top level of the vCenter, each host object (not cluster) is given permissions, and in the VM view the folders have no permissions.  

    If you don't want to monitor the hosts themselves that host said VMs either, you can literally just take the permission away from that cluster or clusters.  The important thing is not giving permissions to your entire vCenter at the top level.

4 Replies

Sort By
  • gtrietsc's avatar
    gtrietsc
    Icon for Contributor II rankContributor II
    3 months ago

    What we have done is not grant permissions to the SL1 account to view the objects in vCenter.  So instead of seeding the permissions at the top level of the vCenter, each host object (not cluster) is given permissions, and in the VM view the folders have no permissions.  

    If you don't want to monitor the hosts themselves that host said VMs either, you can literally just take the permission away from that cluster or clusters.  The important thing is not giving permissions to your entire vCenter at the top level.

    • mtate's avatar
      mtate
      Icon for Contributor II rankContributor II
      3 months ago

      Thank you for that, had not thought about doing it that way so that is really appreciated.

  • cohiker62's avatar
    cohiker62
    Icon for Contributor rankContributor
    2 months ago

    We have this issue with Veeam replicas (they are all copies that are OFF) - we've configured vcenter/veeam to create replicas into a specific resource pool that has its collections all turned off. We do this also for vm's we turn off but haven't yet deleted - they get migrated to a resource pool "dead pool" that also has its collections turned off. What I haven't been able to figure out is how to deal with Templates. They keep showing up in SL1 as vm's that should be running but aren't. When the Templates are converted to a VM they are in a resource pool that doesn't have collections running. As soon as I make them a template again, SL1 wants to complain.

    I'm hoping that this PPK gets re-written soon in to some low-code so that we can actually modify its behavior.