LogicMonitor v.192 is scheduled to roll out to customer portals from September 20, 2023 through October 2, 2023.
- Feature Highlights: VMware vSphere 8 support and automated monitoring. New Test and Steps tabs for Synthetics resources.
- General Updates: Improvements to the display of topology connections, support for managing alert rules with the Terraform integration, and more.
- Updated Monitoring: New modules to monitor AWS MSK clusters, Cisco Catalyst switches, Kubernetes internal etcd clusters, Nimble volume usage over SSH, and VMware vSphere 8.
VMware vSphere 8 Support and Automated Onboarding
New modules add official support for vSphere 8 (ESXi & vCenter) and introduce a fully automated recurring method of communicating with VMware vCenter to discover, onboard, and organize vCenter-managed ESXi hosts and mission critical virtual machine Resources based on customer-provided filters such as naming conventions, power state, and vCenter tags. For more information, see VMware vSphere Monitoring in the product documentation.
New Test and Steps Tabs for Synthetics Resources
You can view detailed information of all your website’s operations that are logically categorized into Test and Steps. Each Test is treated as an individual device, and each Test consists of multiple Steps which represent the different operations of your website. The displayed information includes a unique colored graph allowing you to differentiate the different operations for your website and a table displaying the runtime data for each Step. For more information, see Viewing Test and Steps Tab Data in the product documentation.
- Fixed and issue where the Absolute Delta threshold was falsely alerting. Now when the Absolute Delta is used as a comparison method for an alert threshold, we will treat a resulting trigger calculation of NaN as a 0, since NaN indicates that there was no change in the data.
- Fixed an issue that caused duplicate logs to be ingested for certain log types.
- You can now add, remove, and update Alert Rules with the Terraform integration.
- When you disabled alerts at the parent level in the Alerts Threshold Reports, the alerts were still enabled in the child datasources and instances. Fixed this issue to correctly show the alerting disabled in child datasources and instances.
- The Accounts Information page now displays the correct device count, which is the total of Cloud Resources Monitored with a Collector and Standard Devices.
- Manual edges in the topology are now highlighted when in Manual Mapping mode so you can differentiate them from automatic connections.
- Fixed an issue in Topology where it was not possible to select some instances with a colon “:” in the name in Add dialog.
New UI Beta
Disclaimer: This feature is currently in Beta. In the coming weeks, this beta will be made available for all users. For more information, see New UI Overview in the product documentation.
- Removed text limits for all report types. You can find report-specific threshold limits in the documentation for each report type. For more information, see Reports New UI Overview in the product documentation.
- Added validation to the dynamic thresholds configuration form fields that will prevent users from saving entries with invalid values, such as negative values in lower and upper bound fields.
- If you receive a 401 status on a new UI page, you may need to refresh the page and log back into your LogicMonitor portal.
- Optimized the behavior of the stack view for Graphs to improve the representation of the data. Previously, the stacked graph view was difficult to use because some datapoints overlapped over others.
- Made the Graphs tab the default view for Resources and DataSources.
- You should no longer see a plus sign (Add new) button on the Instances tab for a module when Active Discovery is set to Yes.
- When you enable OpsNotes, you should see them applied across all groups, resources, and so on, so that you don’t have to enable it each time.
- Fixed an issue to ensure that OpsNotes created in the Legacy UI display as expected in graphs and lists after you enable the new UI.
- Fixed an issue where Test Script for Groovy scripts in PropertySources was not working.
- Fixed an issue to prevent users from creating static thresholds that did not contain at least one severity value, and from creating more than one All Day threshold. There are now checks to ensure that you include at least one severity field, and you will not be able to Save an All Day threshold if one already exists.
New and updated LogicModules are available for you to import from the LogicMonitor Public Repository. This section lists the LogicModules that are new in this release, updated in this release, or will be removed in a future release. Changes related to the LogicModule feature will be listed under General Updates.
|New modules to support MSK Provisioned and Serverless Clusters separately, replacing AWS_MSK_Cluster. See related updates under Deprecated Modules.|
|New monitoring for Cisco Catalyst Switch of 2000, 8000 and 9000 series.|
|New monitoring for internal etcd cluster.|
|An alternative version of “Nimble Volume Usage” that utilizes SSH instead of SNMP for data collection.|
|New modules that introduce official support for VMware vSphere 8.x. See related updates under Deprecated Modules.|
|Added Graph improvements.|
|Updated to handle negative ASN.|
|Updated complex datapoint in Cisco_PowerOverEthernet to return 0 if no data exists. Added value check for PSETotalPower to prevent divide by zero errors in Cisco_Catalyst_PowerOverEthernet.|
|Updated complex datapoint calculation to prevent alerting on server redirects.|
|New datapoints for health check on ingress endpoints.|
|Updated Limits Requests in Kubernetes Pod.|
|Updated description for Azure Service Bus Module to reflect which datapoints get populated only for certain SKUs.|
|Several updates including property handling changes that can result in removal of instances and loss of data history. Set the property mssql.onlyAlwaysOnDatabases=true on the virtual network name resource of the cluster prior to updating to prevent potential instance loss.|
Previous modules only used one SQL Listener. In installations where multiple listeners are used, this resulted in return duplicate data for each Listener, including duplicate alerts. These updates correct this with each listener only monitoring databases assigned to it. Databases not assigned to any listener will not be monitored.
|Updated to be aware of whether database is “Always On”.|
|Updated to remove instances that do not have a JDBC connection string configured. Will now only alert on devices already configured and running. No instances will be created until a successful connection to the SQL Server is found.|
|Updated technical notes for PaloAlto_FW_BGP to include that the module does not support devices with advanced routing enabled.|
|Removed auto.rubrik.job_monitoring from the appliesTo since it was not being applied by any core modules and prevented this module from applying to devices.|
|Updated max valid values set for InOctets, OutOctets, InMbps, OutMbps to filter out graph spikes from 32-bit counter rollovers.|
|Updated to exclude null wildalias values, and to create instances for ports detected by the Device_BasicInfo module using auto.network.listening_ssl_ports property, while filtering out unsupported protocols such as LDAP.|
|Updated modules optimized for vCenter Server Appliance 6.7 through vCenter Server 8.0.x and ESXi 6.5 through 8.0.x.|
|Update addERI_Juniper_Mist_Device to detect Access Point devices and assign them ‘Wireless’ ERT, which has a new icon.|
This table lists LogicModules that we are deprecating in this release. This means that these LogicModules will be removed in a future release. If available, a replacement LogicModule is listed. For the history of deprecated modules, see Deprecated LogicModules.
Deprecation -> Replacement
|Details||End of Support Date|
Zoom_Room_Issues -> SaaS_Zoom_RoomIssues
Zoom_Room_Status -> SaaS_Zoom_RoomStatus
Zoom_Service_Status -> Saas_Zoom_ServiceStatus
Zoom_SubAccount_Utilization -> SaaS_Zoom_SubAccountUtilization
Zoom_User_MeetingsQos -> Saas_Zoom_MeetingQos
Zoom_User_Stats -> SaaS_Zoom_UserStats
|The deprecated modules use JWT, an authentication method that Zoom is planning to turn off on on September 1, 2023. For more information, see Zoom Developer Documentation.|
Zoom monitoring remains available via the LogicMonitor SaaS integration.
|August 31, 2023|
AWS_MSK_Cluster -> AWS_MSK_Cluster_Provisioned and AWS_MSK_Cluster_Serverless
|AWS_MSK_Cluster is replaced by 2 datasources that support MSK Provisioned and Serverless Clusters separately.||September 1, 2023|
VMware_ESXi_DatastoreCapacity -> VMware_ESXi_DatastoreUsage
VMware_ESXi_DatastorePerformance -> VMware_ESXi_DatastoreThroughput
VMware_ESXi_HardwareHealthSensors -> VMware_ESXi_HardwareHealthSensor
VMware_ESXi_HardwareSensorFans -> VMware_ESXi_HardwareHealthSensor
VMware_ESXi_HardwareSensorPower -> VMware_ESXi_HardwareHealthSensor
VMware_ESXi_HardwareSensors -> VMware_ESXi_HardwareHealthSensor
VMware_ESXi_HostCPUCores -> VMware_ESXi_LogicalProcessors
VMware_ESXi_HostInterfaces -> VMware_ESXi_NetworkInterfaces
VMware_ESXi_HostPerformance -> VMware_ESXi_CPU, VMware_ESXi_Disks, VMware_ESXi_Memory
VMware_ESXi_NetworkStatus -> VMware_ESXi_NetworkState
VMware_ESXi_ObjectCount -> VMware_vSphere_Info (PropertySource)
VMware_ESXi_Resources -> VMware_ESXi_CPU
VMware_VCSA_Backups -> VMware_vCenterAppliance_Backup
VMware_VCSA_CPU -> VMware_vCenterAppliance_CPU
VMware_VCSA_DiskPerformance -> VMware_vCenterAppliance_DiskPerformance
VMware_VCSA_FilesystemCapacity -> VMware_vCenterAppliance_FileSystemPartitions
VMware_VCSA_HealthStatus -> VMware_vCenterAppliance_HealthStatus
VMware_VCSA_Memory -> VMware_vCenterAppliance_Memory
VMware_VCSA_Network -> VMware_vCenterAppliance_NetworkInterfaces
VMware_VCSA_Services -> VMware_vCenterAppliance_Services
VMware_VCSA_Swap -> VMware_vCenterAppliance_FileSystemSwap
VMware_vCenter_AdmissionControl -> VMware_vSphere_HighAvailability
VMware_vCenter_ClusterPerformance -> VMware_vSphere_Clusters
VMware_vCenter_DatastoreCapacity -> VMware_vSphere_DatastoreUsage
VMware_vCenter_DatastoreClusters -> VMware_vSphere_DatastoreClusters
VMware_vCenter_DatastorePerformance -> VMware_vSphere_DatastoreThroughput
VMware_vCenter_DatastoreStatus -> VMware_vSphere_DatastoreStatus
VMware_vCenter_HANodeHealth -> VMware_vCenterAppliance_HighAvailability
VMware_vCenter_HAStatus -> VMware_vCenterAppliance_HighAvailability
VMware_vCenter_HostStatus -> VMware_vSphere_HostStatus
VMware_vCenter_NetworkStatus -> VMware_vSphere_NetworkState
VMware_vCenter_ObjectCount -> VMware_vSphere_Info
VMware_vCenter_ResourcePools -> VMware_vSphere_ResourcePools
VMware_vCenter_VMDiskCapacity -> VMware_vSphere_VirtualMachineDiskCapacity
VMware_vCenter_VMInterface -> VMware_vSphere_VirtualMachineNetworkInterface
VMware_vCenter_VMPerformance -> VMware_vSphere_VirtualMachinePerformance
VMware_vCenter_VMSnapshots -> VMware_vSphere_VirtualMachineSnapshots
VMware_vCenter_VMStatus -> VMware_vSphere_VirtualMachineStatus
VMware_vSphere_VMperformance -> VMware_ESXi_VirtualMachinePerformance
VMware_vSphere_VMsnapshots -> VMware_ESXi_VirtualMachineSnapshots
VMware_vSphere_VMstatus -> VMware_ESXi_VirtualMachineStatus
VMware_vSphere_vDiskCapacity -> VMware_ESXi_VirtualMachineDiskCapacity
addCategory_vCenterHA -> addCategory_vCenter
VMware_ESXi_Topology -> VMware_vCenter_Cluster_Topology & VMware_vCenter_Datastore_Topology
VMware_vCenter_Network_Topology -> VMware_vSphere_Network_Topology
VMware_vCenter_VM_Topology -> VMware_vSphere_VirtualMachine_Topology
|The deprecated modules have been superseded by new modules that are optimized for vCenter Server Appliance 6.7 through vCenter Server 8.0.x and ESXi 6.5 through 8.0.x. The new modules are named to reflect what they monitor.||September 15, 2023|
In this section, you will find announcements about upcoming beta features, updates about ongoing beta features, and information about the end-of-support for existing features.
Disclaimer: This feature is currently in Beta. Enterprise customers that are currently active in the New UI Beta are eligible to participate.
You can now view additional correlated metrics that are related to a numeric metric in alert. The new Datapoint Analysis feature will pull in relevant datapoints that are highly correlated to the alerting datapoint, and generates a correlation score. This correlation score is calculated based on datapoints retrieved by several different strategies like datapoints from the same instance. The higher the correlation score for a particular datapoint, the more correlated that datapoint is to the datapoint associated with the alert.
New Cisco Catalyst-SD-WAN (formerly Viptela) Modules
In a future release, LogicMonitor will introduce new device-based modules that support Cisco SD-WAN Bulk API versions 20.6.x to 20.12.x (current release). LogicMonitor will provide a new Enhanced Script NetScan to automate discovering and onboarding each vEdge, cEdge, vSmart, and vBond device and to organize the Resources in Groups by SD-WAN Site ID. These modules provide new features, an intuitive user experience, simplified ServiceNow CMDB Integration, and support for core LM Envision features like Network Traffic Analysis, Log Analysis, and Role Based Access Control.
New Cisco Meraki Modules
In a future release, LogicMonitor will introduce new device-based modules that support Meraki Dashboard API 1.36 (current version). LogicMonitor will provide a new Enhanced Script NetScan to automate discovering and onboarding Meraki Security Appliance, Switch, Wireless Access Point, and Smart Camera devices and to organize the Resources in Groups by Meraki Organization and Network name. These modules introduce new features, an intuitive user experience, simplified ServiceNow CMDB Integration, and support for core LM Envision features like Network Traffic Analysis, Log Analysis, and Role Based Access Control.