Hi,In vSphere I have added a local account (Read-only) for LM to poll it. This works fine.However when trying to add an actual ESX host I get access denied. In vSphere for each host, I can see that the local account I created has propagated down just fine, so what else can be the cause?When the Add Device Wizard fails, if I manually specify the creds it still fails, but I can manually specify the ESX host built-in root account and it works fine. So do we need to additionally have a local user account on each ESX host, and that the vSphere inherited perms don’t work for LM?Thanks

I’ve only gotten it to work by adding a read-only user within the ESX Host directly.

Taking a quick peak at a sampling the latest vmware datasource code in Exchange. It looks like:VMware_ESXi_* looks at esx only VMware_vSphere looks at vcenter first, then vcsa, then esx VMware_vCenterAppliance_* looks at vcsa first, then vcenter, then esx VMware_vCenter_* looks at vcenter first, then vcsa, then esxI didn’t really test these, but I would make sure you have the latest Vmware PropertySources and DataSources.

Not sure how up-to-date these are, but LM has a repo of dashboards, there might be an updated one:https://www.logicmonitor.com/dashboards/ https://github.com/logicmonitor/dashboards

I’m not aware of any kinda versioning or updating system for dashboards. You can import/export dashboards via json but I believe some widgets can’t be exported fully. Atleast for me, while I might first start with a built-in or github dashboard, I’ve heavily modified them for our needs. Luckily it’s easy to clone/move widgets between dashboards so I might import a new github dashboard and clone over the widgets I want, into what I’ve already have.One option is setting up a template dashboard group with various standard dashboards you want, for each customer with some customer-based tokens. When you onboard new customers just clone the whole group. You can then focus mostly on keeping the template up-to-date and “upgrade” existing customers by replacing the old ones with the newer template ones. You still need to deal with any per-customer customization that have been made. But that is the case with a lot of things and hopefully you don’t need to do that too much.

I’m not aware of any kinda versioning or updating system for dashboards. You can import/export dashboards via json but I believe some widgets can’t be exported fully. Atleast for me, while I might first start with a built-in or github dashboard, I’ve heavily modified them for our needs. Luckily it’s easy to clone/move widgets between dashboards so I might import a new github dashboard and clone over the widgets I want, into what I’ve already have. One option is setting up a template dashboard group with various standard dashboards you want, for each customer with some customer-based tokens. When you onboard new customers just clone the whole group. You can then focus mostly on keeping the template up-to-date and “upgrade” existing customers by replacing the old ones with the newer template ones. You still need to deal with any per-customer customization that have been made. But that is the case with a lot of things and hopefully you don’t need to do that too much. We don’t even clone them by default. Since we standardize our folder structures and have dynamic rollup folders, we simply have a curated dashboards area. They are pointing to */ZZZ_Firewalls_PaloAlto/* for example for a Palo Alto dashboard. The clients’s roles are restricted to their devices, so it just works. We also give them their own folder where they can make their own, or clone out one of our curated dashboards.

VMware ESX host (no vSphere/vCenter) auth problem

Justin_Lanoue
Neophyte
11 months ago
I’ve only gotten it to work by adding a read-only user within the ESX Host directly.
Mike_Moniz
Professor
11 months ago
Taking a quick peak at a sampling the latest vmware datasource code in Exchange. It looks like:
VMware_ESXi_* looks at esx only

VMware_vSphere looks at vcenter first, then vcsa, then esx

VMware_vCenterAppliance_* looks at vcsa first, then vcenter, then esx

VMware_vCenter_* looks at vcenter first, then vcsa, then esx
I didn’t really test these, but I would make sure you have the latest Vmware PropertySources and DataSources.
Mike_Moniz
Professor
11 months ago
Not sure how up-to-date these are, but LM has a repo of dashboards, there might be an updated one:
https://www.logicmonitor.com/dashboards/

https://github.com/logicmonitor/dashboards
Mike_Moniz
Professor
11 months ago
I’m not aware of any kinda versioning or updating system for dashboards. You can import/export dashboards via json but I believe some widgets can’t be exported fully. Atleast for me, while I might first start with a built-in or github dashboard, I’ve heavily modified them for our needs. Luckily it’s easy to clone/move widgets between dashboards so I might import a new github dashboard and clone over the widgets I want, into what I’ve already have.
One option is setting up a template dashboard group with various standard dashboards you want, for each customer with some customer-based tokens. When you onboard new customers just clone the whole group. You can then focus mostly on keeping the template up-to-date and “upgrade” existing customers by replacing the old ones with the newer template ones. You still need to deal with any per-customer customization that have been made. But that is the case with a lot of things and hopefully you don’t need to do that too much.
Joe_Williams
Professor
11 months ago

I’m not aware of any kinda versioning or updating system for dashboards. You can import/export dashboards via json but I believe some widgets can’t be exported fully. Atleast for me, while I might first start with a built-in or github dashboard, I’ve heavily modified them for our needs. Luckily it’s easy to clone/move widgets between dashboards so I might import a new github dashboard and clone over the widgets I want, into what I’ve already have.

One option is setting up a template dashboard group with various standard dashboards you want, for each customer with some customer-based tokens. When you onboard new customers just clone the whole group. You can then focus mostly on keeping the template up-to-date and “upgrade” existing customers by replacing the old ones with the newer template ones. You still need to deal with any per-customer customization that have been made. But that is the case with a lot of things and hopefully you don’t need to do that too much.

We don’t even clone them by default. Since we standardize our folder structures and have dynamic rollup folders, we simply have a curated dashboards area. They are pointing to */ZZZ_Firewalls_PaloAlto/* for example for a Palo Alto dashboard. The clients’s roles are restricted to their devices, so it just works. We also give them their own folder where they can make their own, or clone out one of our curated dashboards.
Anonymous
11 months ago
def user = hostProps.get('vcenter.user') ?: hostProps.get("vcsa.user") ?: hostProps.get("esx.user")
This simply means use vcenter.user if it exists, If not, use vcsa.user if it exists. If not, use esx.user.
Mike_Moniz
Professor
11 months ago
VMware_vCenter_VMInterface is deprecated, so you may have old DSes that have been replaced with newer ones. See https://www.logicmonitor.com/support/logicmodules/about-logicmodules/deprecated-logicmodules
P.S. Welcome to the fun of DataSource upgrades :)
ldoodle
Advisor
11 months ago

def user = hostProps.get('vcenter.user') ?: hostProps.get("vcsa.user") ?: hostProps.get("esx.user")

This simply means use vcenter.user if it exists, If not, use vcsa.user if it exists. If not, use esx.user.

yeah I realise that. I’m used to other programming languages from my day job.
ldoodle
Advisor
11 months ago

P.S. Welcome to the fun of DataSource upgrades :)

Oh wow do I know now. A couple of widgets have lost their data now so I have to rejig them!
Anonymous
11 months ago
One option is setting up a template dashboard group with various standard dashboards you want, for each customer with some customer-based tokens. When you onboard new customers just clone the whole group.
This is what we do too. The only difference is that we do it via the api, but Mike may be doing that too.