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).
When Will My Module Toolbox Work Properly?
So we recently received a banner in one of our portals stating that in a future release the LogicModules section will no longer be available. This concerns us greatly as I noticed something after I just had a new portal spun up. I logged in, went to the Modules section in the new UI and told it to show me all of our outdated items. Nothing shows up. I then went into the Exchange, told it to show me all of the Installed and Update Available. Nothing shows. I also checked for anything Official that isn’t installed, and nothing shows up.So I naturally go the legacy route, load up DataSources, and tell it to look at the repository. Lo and behold, I have 85 DataSources. Some are new, some are updated. We were told at one point that the Modules/Toolbox/Exchange area look at a different repository, so we gave the benefit of the doubt and checked one of the new modules and an updated module, and both were 3 months old and not showing up in the new UI. Stu brought up some concerns as well inUpdates to modules showing in repo but not modules toolbox | Community (logicmonitor.com), but I didn’t want to necro post with a slightly different issue.Typo in several modules fixed
FYI, LM pushed out a bunch of modules containing a typo in one of the tokens in the alert message. ##DESCRIPTION## isn’t a valid token and ##DSIDESCRIPTION## should be used instead. This has been corrected in the following modules: Aruba_ClearPass_AccessAuthorization Aruba_ClearPass_DiskMemoryUsage Aruba_ClearPass_NetworkTraffic Aruba_ClearPass_PolicyServer Aruba_ClearPass_ProtocolStats AWS_ElasticTranscoder CiscoSLA_jitter- Logstash_ConfigReload_Stats NetApp_7mode_SnapshotScheduler OpenGear SerialPort VMware_ESXi_HardwareHealthSensor VMware_vCenterAppliance_Backup VMware_VCSA_BackupInstances Whois_TTL_ExpiryParity? What is that?
So, this is happening at some point. Today, given the release of several updates to modules, I decided to abandon my really good workflow and the coolest tool LM never built in favor of the modules toolbox. Sigh. There’s no option that I can find to “show associated devices”, which in the old UI showed a list of devices with their associated instances. You could even filter to only show those devices that had instances. There was a CSV download option. It was great because you could tell the difference between a module applying to 500 devices that have instances and applying to 500 devices that didn’t have any instances. It’s the difference between impact and no impact. Later, I needed to clone at propertysource. The existing one was fine, just needed to add some stuff for a different purpose. Guess what there is no button for in the module toolbox? Cloning a module. On the plus side, there is now a “use status” column for display and filtering. That helps a ton. This isn’t a parity issue, but there’s a new “deprecated” indicator for those modules that have been deprecated. You know what you can’t find without going somewhere else? Which module replaces it. I really, really hope the old ship doesn’t get scuttled before the new ship can even float.Alerts coming from seemingly one DS when they actually come from multiple
I’ve already opened a case with support to see if anyone knows anything on their side, but figured I’d ask here/make others aware: When looking at some of my alerts this morning, I noticed that when Ifiltered by "LogicModule == VMWare VM Snapshots", some alerts were from datapoints called"AgeInHours" and some were from datapoints called "age_hours". I wondered what the difference was between these two datapoints and why one DS would have two different datapoints (with alert generating thresholds) with names so similar. Turns out even though the alert page shows all these alerts coming from the "VMware VM Snapshots" DS, they are in fact coming from multiple DataSources: VMware_vCenter_VMSnapshots and VMware_vSphere_VMsnapshots. Those two DSs happen to share the same display name. I get why they do, but filtering by display name (which isn't guaranteed to be unique) isn't always desirable. I get why it could be handy, but the alerts page (and header graph) give a false impression that these belong to a single logicmodule, when in fact they don't. This will be a big problem when I'm trying to tune thresholds for these. I'll tune the thresholds, but some of the alerts will be unchanged, despite me thinking I've modified the thresholds. If anyone knows: How can I filter for just one LogicModule or the other without including alerts from both (without explicitly defining a datapoint filter)? How can I make the header graph show how many are from each DS?Finding VMware's most recent vulnerability
I woke up this morning to an email pointing me to this:https://www.vmware.com/security/advisories/VMSA-2021-0002.html My boss -Can LM tell us which ones need attention? We’d like to notify our customers proactively. Me - Sure! Oh wait, I only have version info for the ESX servers. I’ll have to build out something to grab the vCenter versions. So, I built a custom property source. AppliesTo: system.virtualization =~ "VMware ESX vcenter" && (vcsa.user || esx.user) && (vcsa.pass || esx.pass) Then the script looks like this: /******************************************************************************* * © 2023 Aqueduct Technologies Inc. * * External Resources: * - https://developer.vmware.com/apis/vsphere-automation/v7.0U1/appliance/rest/appliance/system/version/get/ * ******************************************************************************/ import groovy.json.JsonSlurper user = hostProps.get("vcsa.user")?: hostProps.get("esx.user") pass = hostProps.get("vcsa.pass")?: hostProps.get("esx.pass") host = hostProps.get("system.hostname") session_endpoint = "/rest/com/vmware/cis/session" //endpoint for establishing an ssl session vsphere_version_endpoint = "/rest/appliance/system/version" //endpoint for determining vsphere version jSlurp = new JsonSlurper() globalHeaders = [:] genSessionId()//get session ID for future API requests try{ def resp = httpRequest(vsphere_version_endpoint) if (!resp) {return 1} println("auto.vcenter.version=${resp.version}") } finally{deleteSessionId()} return 0 def genSessionId(){ String auth = "Basic " + "$user:$pass".getBytes().encodeBase64().toString() def headers = ["Authorization": (auth)] def resp = httpRequest(session_endpoint, headers, 'POST') globalHeaders.put('Cookie', "vmware-api-session-id=${resp as String}") } def deleteSessionId(){ httpRequest(session_endpoint, [:], 'DELETE') } def httpRequest(def endpoint, Map<String, String> headers = [:], def method = 'GET', String query = null){ URI _uri = new URI('https', null, host, 443, endpoint, query, null) def _session = _uri.toURL().openConnection() _session.setRequestMethod(method) (headers + globalHeaders).each { k, v -> _session.setRequestProperty(k, v) } def response = _session.getInputStream().getText() _session.disconnect() return (response) ? jSlurp.parseText(response).value : null } If you don’t have one under /Devices by Type, create a dynamic group for ESX hosts and another dynamic group for vCenter. We called ours “VMware Hosts” (AppliesTo system.virtualization =~ "VMware ESX host") and “VMware vCenters” (AppliesTo system.virtualization =~ "VMware ESX vcenter") respectively. Then create a Resource Inventory report where the Resource Group is “Devices by Type/VMware*”. Add the system.virtualization, auto.vcenter.version, and system.version properties and run it. Voila, you now know the version numbers of your ESX and vCenter resources and you can compare that to the versions in the VMware Advisory.
My Module Toolbox Pro-Tips
As a Customer Success Manager here at LM, I wanted to share a few key features found in our new Module Toolbox that have made keeping LogicModules up to date easier than ever! Search functionality Upon opening your Module Toolbox (found among your tabs under the Reports tab), you will notice there is a search bar in the top left. This will allowyou to search for any specific modules instead of spending time combing through looking for the one you need! Multiple filters You can now filtermodules you’re searching for by type (datasource, eventsource, configsource, etc.) as well as by customized, skipped updates, author, group, status and report! Bulk updating You now have the ability to update your modules in bulk(-given that you don’t have any customizationson the modules you have selected). This is going to savetime when it comes to keeping your modules up to date, rather than having to update them one by one.If you have customized modules, simply select the filter for “customized” and select “no”. From there you can select all and update. ba-da-boom! Customization preservations This is one that so many of our customers have been asking for. When updating a customized module, again, select the filter for “customized” and select “yes”. From there you will click the update button (depicted as an up arrow inside a circle) on the module you’d like to update. Review any changes made to the module in the diff viewer, click final review and then you will see a “Preservations” option on the right hand side which allows you to preserve customizations made to that particular module. You can currently preserve settings for Active Discovery filters, AppliesTo, Collection Interval, Discovery Interval, Display Name, and Group. No more updating the module to only have to go back in and rewrite all your customizations! Happy updating! :)Does this update make any sense?
Take a look at the Cisco_UCCX_LatestBackup DS. It’s got a threshold of “= 2 3” which is great because the description says: Status of the most recent backup operation. Possible statuses include: 0: Unknown/In Progress 1: Success 2: Warning 3: Error However, the most recent update changed the max valid value for that datapoint to 1 instead of 3. So, that threshold is never gonna trigger. Just wondering if anyone knows if there’s a reason for this internally conflicting datapoint configuration or if somebody just goofed.
