Resolution for: "VMware Troubleshooter-Unable to get list of VCSA metrics Alert"
We've started having this VMware Troubleshooter alert "Unable to get list of VCSA metrics Alert". The notes mention ensuring the user is assigned to SystemConfiguration.Administrator SSO group. We've confirmed this is already in place and are confused because the membership of the user hasn't changed. Has anyone else experienced this and resolved successfully? All other vCenter and vSphere modules that I have spot-checked are polling data successfully.ESX vs vSphere data discrepancy
Hi, We use VMWare and vSphere and have LM configured to poll the vSphere clusters to get the data such as VM Performance. We then looked at the various ESX modules vs vSphere modules to see what was different. When we looked at the ESXi Modules, there is a disclaimer on them that says: By default this module is disabled due to monitoring the same metrics as VMware_vSphere_VirtualMachinePerformance. We turned on the VMware_ESXi_VirtualMachinePerformance module and compared that to the data in the VMware_vSphere_VirtualMachinePerformance module and assumed we'd see similar information. However, the information is actually very different. Does anyone know how these work and why the information that says it's the same would actually not be?
What is the correct way to exclude VMWare folders from the new script netscan?
I am trying to use the netscan to discover VM/ESXi hosts within my vCenter applicances. I want to exclude a few specific folders when viewing from "VM and Templates" view. It looks like it supports excluding folders based on the doc, VMware vSphere Monitoring | LogicMonitor I have added this filter attribute 'vcenter.folder' and in the scan it looks like this. This doesnt seem to work though. Ive tried both 'contain' and 'notcontain' and neither are excluding these folders. Any ideas?VMWare Check Datastores for unusual files/file extensions.
I am looking to implement a some form of monitoring for when files on a datastore become renamed or appear with file extensions that are not part of a predefined list(.vmdk, .vmx, etc...). The 2 ways I am considering are via a config source or just a regular datasource and I am trying to weigh out the pros and cons of each. I don't think using SSH with a config source will work because our monitoring accounts are all read only and I'm not sure if that level of permissions includes SSH access. On the other hand a config source can check quickly and effectively where as using a datasource with Active Discovery is limited to 15 minutes if it were in fact wanting to discover new instances of files with abnormal file extensions. Can you implement a config source that uses the SDK like the legacy VMWare modules in lieu of SSH? Looks like you can. That might be the way to go. Looks like I would want to use "HostDatastoreBrowser" from the SDK. What would you guys do?New VMware modules dropped
Did anybody else notice the ~44 new and ~5 updated modules around VMware dropping in the last hour or so? Does anyone know how to implement these new modules? Since there was talk of making the instances into resources I don’t want to just bring them in without knowing how it’s going to mess with my device list (which is tightly bound to billing for us).Datasource to get Uptime of VMWare vCenter Appliance
I cannot find a DataSource to build off to grab the uptime of our vCenter appliances. I am able to get ESXi hosts uptimes with: import com.vmware.vim25.mo.*; import com.santaba.agent.groovyapi.esx.ESX; def host = hostProps.get("system.hostname"); def user = hostProps.get("esx.user"); def pass = hostProps.get("esx.pass"); def addr = hostProps.get("esx.url") ?: "https://${host}/sdk"; def svc = new ESX(); svc.open(addr, user, pass, 10 * 1000); // Timeout in 10 seconds def rootFolder = svc.getServiceInstance().getRootFolder(); def hosts = new InventoryNavigator(rootFolder).searchManagedEntities("HostSystem"); hosts.each { esx -> def uptimeinSeconds = esx.summary.quickStats; println "UpTimeInSeconds=${uptimeinSeconds.uptime}"; } return 0; but cannot seem to adapt this for vCenter Appliances. Any help would be appreciated!Checking Reboot of VMs
Has anyone had any luck monitoring VMStatus for reboots without using the DaysSinceLastReboot? as this gives a false reading, as it kicks in when the VM is vMotioned. I have tried the GuestState but it looks like the GuestOS isnt in the state for long enough for that to trigger
