v.200 Release Notes
Last updated on 27 March, 2024Highlights
- Feature Highlights: Cisco Catalyst Center’s Intent API Modules, Addition of Alert Tuning Parameters
- General Highlights: New supported cloud services, Delta Support for API, Identify Usage of LogicMonitor REST API Versions based on Users
- Monitoring Updates: Monitor Catalyst Wireless Access Points in a Cisco Catalyst Center environment, VMware modules post-release fixes, Added filtering to exclude instances with null values for id or sensor name
Feature Highlights
Cisco Catalyst Center’s Intent API Modules
You can now use new modules for monitoring Wireless Access Points (AP) and Wireless LAN Controllers (WLC) via Cisco Catalyst Center’s Intent API (formerly Cisco DNA Center) with an Enhanced Script NetScan for automated, API-based device discovery. For more information, see Cisco Catalyst Wireless Access Point Monitoring in the product documentation.
Addition of Alert Tuning Parameters
In addition to setting static alert threshold, you can now also set alert tuning parameters that include alert trigger interval, alert clear interval, and no data alert at the resource group, instance group, and instance level. The alert tuning parameters follow the inheritance model, which means if the alert trigger, alert clear, or no data field is set at the resource group level, all nodes under it inherit the value. Currently, this feature is applicable only to DataSource Logic modules. For more details, see Alerts Tuning Tab in the product documentation.
You can also find this feature in the updated LogicMonitor REST API v3 Swagger. To know the impacted endpoints and new fields, see REST API Change Log in the product documentation.
The Alert tuning feature will be rolled out to customers in batches starting in v200. Deployments will continue over the course of several weeks. For any questions, contact your LogicMonitor Customer Support Manager.
General Updates
Alerts
Known Issues
A “request header too large” error appears occasionally when selecting the datapoint analysis button on the Launch from Dashboards feature.
Cloud Monitoring
New supported services and additional updates
New supported services have been added to the Cloud Services and Resource Units tables for AWS, Azure, and GCP. Category, resource units, and billable specifications have been updated for some existing resources
For more information, see Cloud Services and Resource Units in the product documentation
New Enable Collector Debug Default Behavior
“Enable Collector Debug” option is now available in Portal Settings. This option is disabled by default for new accounts. For existing portals, the option is enabled by default to maintain availability of the collector debug facility.
Additional Enhancements
Removed a band factor restriction set to at a global level to make the experience consistent with what can be set at the Device, Instance Group, and Instance level.
Known Issues
Azure Resource Health does not have the option to set Error and Critical Alert level for matching events. It only has the option to set Warning Level.
Dashboards
Additional Enhancements
Using dynamic filters, you can now filter dashboards with inherited resource group properties.
Fixed Issues
- The Type column has been restored. You can sort by the type of SDT that was created. If you do not see the new column “Type” in the SDT table, choose the Show Table Settings Icon then choose “Reset” on Column Settings.
- Graphs now order based on the priority set in the graph definition.
- Fixed an issue that prevented units from converting for the tooltip overlay when hovering over a graph.
Known Issues
- When you are typing a string into a field that has auto-complete capabilities, the cursor moves erratically. This results in difficulty adding text anywhere but at the end of the text field.
- “Default-level” instance group graphs do not generate at the group level.
Identity and Access
Enhancements
- Users now receive an email notification if suspended (manually or automatically) or locked out after exceeding the invalid password limit.
- Made temporary changes to invoice availability in the financial portal. Only new invoices will appear in the portal. Contact Support to get older invoice copies.
- Customers can now identify the username, email, or access-id of users using API v1/2. Contact Support for details.
Modules
Additional Enhancements
Tags are now visible in My Module Toolbox.
Fixed Issues
Fixed an issue that temporarily prevented the In Use column in My Module Toolbox from displaying in the interface.
Resources
Additional Enhancements
When adding a resource dashboard, you must now select the Test AppliesTo functionality before saving to confirm that the AppliesTo function is working as expected. If you add a resource dashboard to a resource that is not included in the AppliesTo logic, the resource dashboard still generates but will remain on the resource you last viewed.
Fixed Issues
Fixed an issue with how the AppliesTo query appears when first opening a resource group.
Known Issues
The IP Address/DNS name is missing from the title bar for a device.
REST API
Delta Support for API
All customers now have access to the Delta API endpoints. To find out the delta (latest changes) of monitored devices, you can use two new endpoints added to /device/devices v3 API.
- GET /santaba/rest/device/devices/delta – Registers delta request and generates a new delta ID. It also returns all devices that match the filter criteria.
- GET /santaba/rest/device/devices/delta/<DELTAID> – Returns devices that have any delta between the last and the current API call.
For more information, see Delta Support for device/devices API in the Product Documentation.
Identify Usage of LogicMonitor REST API Versions based on Users
You can now identify users accessing LogicMonitor REST API versions 1, 2, and 3. To get a report that indicates the user name, email ID, access ID, endpoint name, and date when the endpoint was accessed, contact your Customer Success Manager (CSM).
This report aims to help you identify users who are still using REST API v1 and v2 which are being phased out in October 2024 and encourage them to migrate to the latest API v3.
Usage
Usage Reporting Banner Removal
The banner in Usage Reporting has been removed. You can use the Cumulative Usage graph to view your forecasted usage.
Additional Enhancements
Updated tracking of LM Capacity items vs Licensed Items.
LogicModule Releases
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 in the General Updates section.
New LogicModules
| LogicModule Name | Details |
|---|---|
| 1 DataSources: – AWS_QuickSight_Datasets | Datasource for monitoring AWS QuickSight Datasets |
| 1 DataSources: – AWS_QuickSpice_SPICEServiceLimits | Monitors QuickSight SPICE limits per region. Collection is completed using CloudWatch metrics. |
| 1 DataSources: – AWS_ECR | Gathers Elastic Container Registry performance data as reported by CloudWatch. |
| 1 DataSources: – AWS_ECR_APICallCount | Gathers Elastic Container Registry API usage data as reported by CloudWatch. |
| 1 DataSources: – Oracle_MySQL_Troubleshooter | Troubleshooter module for new MySQL package to assist with resolving configuration issues. |
| 1 PropertySources: – addCategory_LMContainerConfig | Fetch latest lm-container configuration and add as property to Argus KubernetesPod. |
| 6 DataSources: – Cisco_Catalyst_AccessPointHealth – Cisco_Catalyst_AccessPointPerformance – Cisco_Catalyst_AccessPointRadios – Cisco_Catalyst_Center_API – Cisco_Catalyst_WLCHealth – Cisco_Catalyst_WLCPerformance 2 PropertySources: – addCategory_Cisco_Catalyst_Center_Device – addERI_Cisco_Catalyst_Center_Device 1 TopologySources: – Cisco_Catalyst_Center_Topology | Monitors Catalyst Wireless Access Points in a Cisco Catalyst Center environment. |
Updated LogicModules
| LogicModule Name | Details |
|---|---|
| 21 DataSources: – VMware_ESXi_VirtualMachinePerformance – VMware_ESXi_VirtualMachineStatus – VMware_LM_Troubleshooter – VMware_vCenterAppliance_Backup – VMware_vCenterAppliance_CPU – VMware_vCenterAppliance_DiskPerformance – VMware_vCenterAppliance_FileSystemPartitions – VMware_vCenterAppliance_FileSystemSwap – VMware_vCenterAppliance_HealthStatus – VMware_vCenterAppliance_Memory – VMware_vCenterAppliance_NetworkInterfaces – VMware_vCenterAppliance_Services – VMware_vSphere_DatastoreStatus – VMware_vSphere_DatastoreThroughput – VMware_vSphere_DatastoreUsage – VMware_vSphere_HostStatus – VMware_vSphere_VirtualMachineDiskCapacity – VMware_vSphere_VirtualMachineNetworkInterface – VMware_vSphere_VirtualMachinePerformance – VMware_vSphere_VirtualMachineSnapshots – VMware_vSphere_VirtualMachineStatus 1 PropertySources: – VMware_vSphere_Info | VMware modules post-release fixes |
| 1 TopologySources: – Fortinet_FortiGate_SDWAN | Detect local gateway IP from set ERI for more robust tunnel detection. |
| 21 DataSources: – Aruba_EdgeConnect_SDWAN_Health – Cisco_Catalyst_SDWAN_ControllerHealth – Cisco_Catalyst_SDWAN_DeviceHealth – Cisco_Meraki_AccessPointHealth – Cisco_Meraki_CameraHealth – Cisco_Meraki_CellularGatewayHealth – Cisco_Meraki_SecurityApplianceHealth – Cisco_Meraki_SwitchHealth – PaloAlto_Prisma_SDWAN_EdgeHealth – SAP_HANA_BackupAge – SAP_HANA_Connections – SAP_HANA_DatabaseMemoryUse – SAP_HANA_DiskUsage – SAP_HANA_HostResourceUtilization – SAP_HANA_ServiceStatus – SAP_HANA_SystemDatabaseAvailability – SAP_HANA_TableSizeOnDisk – VMware_VeloCloud_EdgeHealth – VMware_VeloCloud_EdgeLinkEventQuality – VMware_VeloCloud_EdgeLinkHealth – VMware_VeloCloud_EdgeLinkMetrics 1 PropertySource: – addCategory_SAP_HANA | Updated to indicate the device’s status as “alive” within LogicMonitor upon receiving a response from the device, regardless of the reported state. |
| 9 DataSources: – PureStorage_ArrayControllers – PureStorage_ArrayPerformance – PureStorage_ArrayUtilization – PureStorage_ComponentStatus – PureStorage_Drives – PureStorage_Temperatures – PureStorage_VolumePerformance – PureStorage_VolumePerformance_API_v1_4 – PureStorage_VolumeUtilization | Updated modules to support devices that do not require cookie to be sent in header fields. |
| 1 PropertySources: – addCategory_Cisco_Meraki_Device 1 TopologySources: – Cisco_Meraki_Topology | Refactored to improve performance so that only the first Meraki org device reports topology. |
| 1 DataSources: – SAP_HANA_Troubleshooter | Removed unused table checks. |
| 1 DataSources: – Cisco_Wireless_AP | Updated ERT from AccessPoint to Wireless. |
| 1 DataSource: – Whois_TTL_Expiry | Included expiration time in the regex search to identify days to expiration. |
| 4 DataSources: – PaloAlto_Prisma_SDWAN_EdgeHealth – PaloAlto_Prisma_SDWAN_EdgePerformance – PaloAlto_Prisma_SDWAN_Overlay – PaloAlto_Prisma_SDWAN_Underlay 1 PropertySource: – addERI_PaloAlto_PrismaSDWAN 1 TopologySource: – PaloAlto_PrismaSDWAN_Topology | Removed properties from appliesTo that were not strictly necessary. Added debug messages when required properties are not provided. |
| 2 DataSources: – Oracle_MySQL_Innodb – Oracle_MySQL_Status | Fixed issue with integer overflow and problem with complex datapoints (moved complex datapoints out of script and back into DataSource definiton with rpn expression). |
| 1 DataSources: – Cisco_TemperatureSensors | Added complex datapoints that correct metric wraps and prevent false alerts. |
| 6 DataSources: – Ubiquiti_UniFi_AccessPoints – Ubiquiti_UniFi_Clients_Wired – Ubiquiti_UniFi_Clients_Wireless – Ubiquiti_UniFi_Security_Gateways – Ubiquiti_UniFi_Sites – Ubiquiti_UniFi_Switches | UniFi OS 3.2.7 no longer responds to the API used by these modules. SNMP monitoring is recommended for clients using Ubiquiti resources running UniFi OS 3.2.7 or higher. Automatically delete instances after 30 days is being disabled due to this change to prevent loss of historical data. |
| 6 DataSources: – Arista_Sensor_Current – Arista_Sensor_DOM – Arista_Sensor_DOMLaserBias – Arista_Sensor_Fans – Arista_Sensor_Temperature – Arista_Sensor_Voltage | Updated Active Discovery to once a day. |
| 1 DataSources: – Cisco_Meraki_API 1 PropertySources: – addCategory_Cisco_Meraki_Device | Added publicIp, wan1Ip and wan2Ip support to Cisco_Meraki_API caching. Added these as properties to addCategory_Cisco_Meraki_Device. Requires latest Meraki netscan code for netscan update — Updated netscan to handle these other IP properties. |
| 1 PropertySources: – addCategory_Puppet | addCategory_Puppet’s HTTP requests now enforce a sensible timeout to reduce collector congestion in certain scenarios. |
| 1 PropertySource: – addCategory_PaloAlto_PrismaSDWAN | Adding handling for null device name. |
| 12 DataSources: – Microsoft_SQLServer_AlwaysOnAvailabilityGroups – Microsoft_SQLServer_AlwaysOnAvailabilityReplicas – Microsoft_SQLServer_AlwaysOnDatabaseReplicaCluster – Microsoft_SQLServer_AlwaysOnDatabaseReplicas – Microsoft_SQLServer_AlwaysOnDatabaseStatus – Microsoft_SQLServer_DatabaseFiles – Microsoft_SQLServer_DatabaseStorage – Microsoft_SQLServer_Databases – Microsoft_SQLServer_FailoverClusterNodeStatus – Microsoft_SQLServer_GlobalPerformance – Microsoft_SQLServer_SystemJobs – Microsoft_SQLServer_Troubleshooter | Updated technical notes to fix misspelling and remove reference to a deprecated PropertySource. |
| 1 DataSources: – VMware_ESXi_SystemHealthSensor | Added filtering to exclude instances with null values for id or sensor name. |
| 1 DataSources: – Aruba_EdgeConnect_SDWAN_Health | Optimized and resolved VRRP data issues. |
| 1 DataSources: – Aruba_EdgeConnect_SDWAN_Performance | Updated the alert threshold for the FreeBuffersCachedSum datapoint and updated virtual datapoint multiplication for proper base64 scaling. |
| 1 DataSources: – VMware_VeloCloud_EdgeLinkEventQuality | Added multi-threading to speed up data processing, increased collection interval from 5 minutes to 10 minutes, and fixed an authentication bug when a cookie expires. |
| 1 TopologySources: – Networking_L2_snmpSwitch | Link LLDP neighbors to standard interfaces as well as LLDP interface. |
| 20 DataSources: – Argus_LM_API – Argus_Runner – Argus_SelfMonitor – Argus_Watcher – Argus_Worker – Kubernetes_API_Server – Kubernetes_Cluster_Aggregate – Kubernetes_Container – Kubernetes_Controller_Manager – Kubernetes_CoreDNS – Kubernetes_Endpoint – Kubernetes_HPA – Kubernetes_Healthz – Kubernetes_Node – Kubernetes_PersistentVolumeClaim_StorageStats – Kubernetes_PingK8s – Kubernetes_Pod – Kubernetes_Schedulers – Kubernetes_Script_Uptime – Kubernetes_etcd 9 PropertySources: – addCategory_KubernetesKSM – addERI_Kubernetes – addERI_Kubernetes_ClusterRole – addERI_Kubernetes_Node – addERI_Kubernetes_Pod – addERI_Kubernetes_Role – addERI_Kubernetes_Service – addERI_Kubernetes_ServiceAccount – selfMonitor_KubernetesKSM 29 TopologySources: – Kubernetes_AWS_Topology – Kubernetes_Azure_Topology – Kubernetes_ClusterRoleBinding_OwnerRef_Topology – Kubernetes_ClusterRoleBinding_Topology – Kubernetes_ClusterRole_OwnerRef_Topology – Kubernetes_CronJob_Topology – Kubernetes_Daemonset_Topology – Kubernetes_Deployment_Topology – Kubernetes_Job_Topology – Kubernetes_Netpol_OwnerRef_Topology – Kubernetes_Netpol_Topology – Kubernetes_Node_KSM_Topology – Kubernetes_Node_Topology – Kubernetes_PC_OwnerRef_Topology – Kubernetes_PDB_OwnerRef_Topology – Kubernetes_PDB_Topology – Kubernetes_PVC_Topology – Kubernetes_PV_Topology – Kubernetes_Pod_KSM_Topology – Kubernetes_Pod_OwnerRef_Topology – Kubernetes_Pod_Topology – Kubernetes_Replicaset_Topology – Kubernetes_RoleBinding_Topology – Kubernetes_Role_OwnerRef_Topology – Kubernetes_Rolebinding_OwnerRef_Topology – Kubernetes_SC_OwnerRef_Topology – Kubernetes_ServiceAccount_OwnerRef_Topology – Kubernetes_Service_Topology – Kubernetes_Statefulset_Topology | Updated description to include lm-container version dependency. |
| 1 PropertySource: – addCategory_ArubaEdgeConnectSDWAN | Updated serial number and OS version property names to display within the UI’s inventory section. |
| 1 DataSources: – VMware_ESXi_CPU | Corrected the logic on counter handling and value parsing; usage and accumulation are now pulled from right counters and allocated to correct CPU core based on the thread number. |
| 2 PropertySources: – addCategory_VMwareBlast – addCategory_PCoIP | Introduced a null check to restrict the addition of system categories to invalid devices. |
| 1 PropertySources: – Config_Juniper_Generic | Common Configs now set a custom escalation command for JUNOS devices. An optional new host property, “config.junos.displayset”, can be used for JUNOS devices. When this property has a value of 1 or true, the configuration is piped to “display set” for formatting prior during config collection. |
| 1 DataSources: – Cisco_Wireless_AP | Updated complex datapoints, tech notes, and descriptions. Graph improvements including legend updates and turning aggregation on for overview graph. |
| 1 DataSources: – Oracle_MySQL_ConnectionStatus | Updated sqlStatusCode datapoint description and alert body to match error messages in code. |
| 1 DataSources: – Ruckus_SZ_DeviceSummary | Added the ability to specify a custom limit for the amount of instances supported by the module. Amount can be specified by adding ‘ruckus.instance_count’ property to the device. The overall limit is restricted by the size of the collector itself |
| 4 DataSources: – Ruckus_SZ_ClusterSummary – Ruckus_SZ_ControllerSummary – Ruckus_SZ_ManagementSummary – Ruckus_SZ_Uptime | Removed underscore from display name. |
| 1 DataSources: – Cisco_DNAC_Devices | Updated ERT to Wireless. |
| 2 DataSources: – CDP_Neighbors – LLDP_Neighbors | Use Wildvalue as Unique Identifier for non data collecting DataSources that assist with topology mapping to correct mapping discrepancies. |
| 10 DataSources: – HP_MSA_Controllers – HP_MSA_Disks – HP_MSA_FRU – HP_MSA_Fans – HP_MSA_PSU – HP_MSA_Ports – HP_MSA_Redundancy – HP_MSA_SASLinkHealth – HP_MSA_VirtualDisks – HP_MSA_Volumes | Updated tech notes to mention that SHA-256 authentication via host property “msa.sha” (set to true to use this authentication type, otherwise defaults to MD5) may be required for MSA 2060 resources. |
| 1 DataSources: – Cisco_IPSec_AggregateTunnels | Added new datapoint and alerting to monitor operation tunnel status. Revised multiple datapoint descriptions. |
| 3 DataSources: – Cisco_Meraki_API – Cisco_Meraki_DeviceInterfaces – Cisco_Meraki_SecurityApplianceUnderlay | To ensure reliable and accurate data collection, irrespective of Meraki MX Security Appliance Model, this update adds appliance uplink API endpoint data collection to Cisco_Meraki_API. Adds support for API underlay data. Note there is a wildvalue change required to handle getting the data from the API. There will be data loss and old instances deleted after 30 days. Also removes packet datapoints as these are not provided by the API. |
| 1 PropertySources: – addCategory_Meraki_API | Only set network props if auto prop or custom prop is successful. Fix type key bug using safenav. |
| 1 PropertySources: – ConfigCheck_3_Exec | Common Config’s config.type.exec override property now correctly works in situations where an enable command was also set. If you used a manually forced config.type.exec property in combination with a property that used an enable command, we will now favor exec type execution. |
| 1 DataSources: – F5_BigIP_PoolMemberStats | Corrected the OID for BytesIn along with checking for the same instances occurring on multiple ports. Multi-port instance will now generate multiple instances, which will invalidate the original. This change will affect history for multiport instances only. |
| 1 DataSources: – VMware_VeloCloud_EdgeHealth | Aligning requests with VeloCloud documentation to request VeloCloud data in UTC. |
| 14 DataSources: – VMware_ESXi_CPU – VMware_ESXi_DatastoreStatus – VMware_ESXi_DatastoreThroughput – VMware_ESXi_DatastoreUsage – VMware_ESXi_Disks – VMware_ESXi_HardwareHealthSensor – VMware_ESXi_HostStatus – VMware_ESXi_LogicalProcessors – VMware_ESXi_Memory – VMware_ESXi_NetworkInterfaces – VMware_ESXi_NetworkState – VMware_ESXi_Power – VMware_ESXi_ResourcePools – VMware_ESXi_SystemHealthSensor | Modified appliesTo to exclude ESXI hosts that use Photon OS |
| 1 DataSources: – OSPF_Neighbors | OSPF Neighbors now uses a non-aggressive retry technique that gives devices more room to recover after a failure. Testing has shown a large drop in NoData when this is used. |
| 1 DataSources: – AWS_DirectConnect | Deprecated datapoint ConnectionCRCErrorCount is replaced by ConnectionErrorCount. |
Deprecated LogicModules
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.
| LogicModule Deprecation | LogicModule Replacement | Details | End of Support Date |
|---|---|---|---|
| 1 DataSources: – Cisco_Meraki_Licensing | N/A | This module will cease to function on February 1st 2024 because it uses the Meraki v0 Dashboard API. | 1/31/24 |
| 2 DataSources: – Kubernetes_ControlPlane – Kubernetes_ControlPlane_Azure | N/A | ControlPlane API has been deprecated from Kubernetes. | 1/2/24 |
| 1 DataSources: – Selenium_Synthetics | SyntheticsSelenium | Reverted deprecation of original module (SyntheticsSelenium) and applied updates there to preserve history and prevent issues with module appliesTo for synthetics collection type. Customers actively using Selenium_Synthetics should work with their CSMs to retrieve historical data prior to deleting Selenium_Synthetics from their portal. | 2/12/24 |
Looking Ahead
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.
LogicModules Migrating to Modules
In a future release, LogicModules will no longer be available from Settings. You can access the Exchange, My Module Toolbox, and all settings for managing modules from Modules in the navigation bar.
For more information, see Modules Overview in the Product Documentation.