Forum Discussion

acampbell78's avatar
acampbell78
Icon for Neophyte rankNeophyte
2 months ago

Adding ESX hosts to LogicMonitor

Can someone advise what is the best practices for adding ESX hosts to LogicMonitor?

One of colleagues contacted me about an isssue where he added ESX hosts for a client without having to define or provide any ESX credentials.

However, once added we could only collect these details regards to host and ping but no data was being pulled in regards to the VMware specific datasources.

The only way to fix this was to manually add the esx.user and esx.pass properties to each ESX hosts in LogicMonitor to start collecting data for the VMware specific datasources.

It seems that somohow it picked up some root ESX account credentials which wer not related to this client.

  • Stuart_Weenig's avatar
    Stuart_Weenig
    2 months ago

    Properties like esx.user and esx.pass can be inherited from group membership. This means you can set the properties at the group level and all resources in the group will inherit those properties as if they were set on the resource (unless there's one defined on the resource, which prevents inheriting it from an ancestor).

    That said, we have not started using the new VMware monitoring modules. Long, unanswered thread here. The idea with the newest iteration of monitoring is that you use a netscan to add all the proper resources. Since the netscan is 10,000,000 lines long, it's difficult to tell what properties will be added automatically, etc.

  • Stuart_Weenig's avatar
    Stuart_Weenig
    Icon for Mastermind rankMastermind
    2 months ago

    Properties like esx.user and esx.pass can be inherited from group membership. This means you can set the properties at the group level and all resources in the group will inherit those properties as if they were set on the resource (unless there's one defined on the resource, which prevents inheriting it from an ancestor).

    That said, we have not started using the new VMware monitoring modules. Long, unanswered thread here. The idea with the newest iteration of monitoring is that you use a netscan to add all the proper resources. Since the netscan is 10,000,000 lines long, it's difficult to tell what properties will be added automatically, etc.