v.142 Highlights:

Platform Enhancements

Alerts

  • (FIX) Alert filtering. Entering multiple exclude criteria for the instance filter (e.g. !(InstanceNameA | InstanceNameB)) was resulting in no filter exclusions for the instance filter. This was impacting both the Alert List widget and the Alerts page. This has been fixed.

Alert Integrations

  • PagerDuty. Collector down alerts are now supported for PagerDuty alert integrations by default. To achieve this, the source fields in LogicMonitor’s default payloads were changed from "source":"##HOST####WEBSITE##" to "source":"##HOST## ##WEBSITE## ##AGENTID## ##AGENT_DESCRIPTION##".

Audit Logs

  • Audit log entry restructure. Audit log entry descriptions for all operations performed on devices, DataSources, and instances have been restructured so as to facilitate parsing of audit logs in a more efficient manner. A typical format of an audit log entry now includes action, type, and description as key-value pairs. Other key-value pairs are additionally present depending upon the operation.

Dashboards

  • (FIX) Gauge widget. The Gauge widget was failing to generate data when “last calendar month” was selected as the value in the Peak time range configuration. This has been fixed.

LM Cloud

  • AWS updates:
    • AWS EMR cluster state mapping. The mapping of EMR cluster states to the system.aws.monitoringstate property has been updated. Previously, the cluster states of STARTING, BOOTSTRAPPING, and WAITING were mapped to a value of “2” which indicates unavailable. With v.142, these states are now being mapped to a value of “1”, which indicates OK, to ensure monitoring is being properly performed on allocated resources.
  • Microsoft Azure updates:
    • New properties discovered for Azure VM. Operating system name and version are now being discovered as instance properties for existing and new Azure VMs. You may find this additional detail helpful when filtering or grouping by properties.
    • (FIX) Azure Storage Service Limits Probe collection method. A recent Azure API upgrade caused the Azure Storage Service Limits Probe collection method to collect service limits per region and not per Azure subscription. As a result, DataSources using this collection method began alerting because expected data was not being returned. This has been fixed.
    • (FIX) Upgraded Azure API. The API used for Azure VMs was upgraded in order to resolve an issue in which properties were being dropped due to discovery timeouts.

LM Container

  • LM Container Argus v4 now available. A new major version of LM Container is now available that provides improved compatibility with LogicMonitor API rate limits; support for pod priority class; and toleration specifications that are helpful for preventing Argus, Collectorset-Controller, and Collector pods from being scheduled on tainted nodes. Because of the extent of the updates in this major version, you will need to opt in to this upgrade. For upgrade details and instructions, see LM Container Argus v4 Release.
  • Discovery filtering. Discovery filtering has been added to LogicMonitor’s Kubernetes monitoring capabilities. This discovery filtering, which is similar to what is available via LM Cloud, can be used to exclude certain resources (for example, QA or dev deployments) from monitoring based on labels. For larger clusters where API server resources are not scalable, discovery filtering can help you better manage API server load due to monitoring. Discovery filtering can be configured in the LogicMonitor UI (from the Add Kubernetes Cluster wizard) or directly in your Helm deployment.
  • (FIX) Dynamic node group queries. Queries for dynamic node groups based on worker role weren’t properly including the correct nodes in some cases; this has been fixed.

LM Exchange

  • (FIX) Automatically Delete Instance slider state. Fixed issue in LM Exchange in which the Automatically Delete Instance on/off slider was visually rendering the state opposite to the actual state.

Network Traffic Flow Monitoring

  • Enhanced filtering at device group level. The filtering options available for filtering network traffic flow data at the device group level are now at functional parity with those available at the device level.

Topology Mapping

  • Node filtering. Node filtering based on edge type has been added to topology maps that display from the Resources page (on the Maps tab).

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, import our new and updated LogicModules to expand and enhance your monitoring coverage.

New LogicModules

  • Arista Switch – 3 DataSources

    Three new DataSources have been released to replace the now-deprecated and more general Arista_Switch_Storage DataSource. The new DataSources (Arista_Switch_FlashStorage, Arista_Switch_Memory, and Arista_Switch_StorageUsage) filter out instances to allow for separate DataSource monitoring of memory, flash storage, and standard storage. Alerts have been added for Arista_Switch_StorageUsage.

  • Fortinet FortiGate – 1 PropertySource, 2 TopologySources

    For improved FortiGate topology mapping operations, two new TopologySources (Fortinet_FortiGate_HA and Fortinet_FortiGate_SDWAN) for generating HA and SDWAN edges respectively have been created. In addition, one new PropertySource (addERI_Fortinet_FortiGate) to support ERI discovery for Layer 2, Layer 3, high availability and SDWAN ERIs has been added.

    Note: As discussed in the Updated LogicModules section, updates to two existing LogicModules are also available for improved FortiGate topology mapping.

  • HPE Nimble – 1 PropertySource

    A new PropertySource named addCategory_NimbleSSH was added to the HPE Nimble monitoring suite. This PropertySource tests SSH access to Nimble devices and applies the “NimbleStorageSSH” category.

    As noted in the Updated LogicModules section, enhancements have additionally been made to several existing HPE Nimble LogicModules.

  • VMware NSX – 6 DataSources, 2 PropertySource, 2 ConfigSources

    Collects metrics for NSX manager system resource utilization and component status; NSX controller resource utilization; uptime and node failover status; and edge service health and interface throughput. Monitors configs for NSX controllers and edge services. For setup and monitoring details, see VMware NSX Monitoring.

Updated LogicModules

  • APC_Environment_Monitor_Humidity- – 1 DataSource

    Fixed unclear descriptions and alert messages on the humidity threshold breach datapoints.

  • AWS_RDS_ServiceLimits – 1 DataSource

    Added missing metric names that were causing data collection to fail.

  • Cisco_FRU_Power – 1 DataSource

    Removed three complex datapoints (operatingStatusAlert*) and moved their alerting to the OperatingStatus datapoint.

    Important: Any instance-level tuning or alert rule configurations currently referencing these three removed complex datapoints will need to be reconfigured to reference the OperatingStatus datapoint. Historical data for the OperatingStatus datapoint will not be impacted, but historical data will be lost for the three removed operatingStatusAlert* complex datapoints.

  • Cisco_NXOS – 1 ConfigSource

    Removed log4j usage due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher; updated filters for the DifferenceTest config check.

  • Citrix_Netscaler – 1 ConfigSource

    Removed log4j usage due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher.

  • DataCore_Symphony_VirtualDisks – 1 DataSource

    Removed unused jackson-databind import to align with Collector versions 29.102 and higher.

  • Dell EMC – 1 PropertySource

    For improved topology mapping operations, updated the addERI_Linux PropertySource to set “Switch” as external resource type for Dell EMC networking devices.

  • Device_BasicInfo – 1 PropertySource

    Updated to use the actual hostname instead of its string representation to generate values for the auto.network.names property. This prevents invalid values from being set for the property due to DNS resolution issues.

  • Fortinet FortiGate – 1 DataSource, 1 PropertySource

    For improved FortiGate topology mapping operations, updates have been made to the Fortinet_FortiGate_HighAvailabilityPeers DataSource and the addERI_Device PropertySource.

    Note: As discussed in the New LogicModules section, three new LogicModules have been released for improved FortiGate topology mapping.

  • HPE_Network_Config – 1 ConfigSource

    Removed log4j usage due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher.

  • HPE Nimble – 5 DataSources, 1 PropertySource

    Updated the AppliesTo statement to use new “NimbleStorageSSH” category set by the newly-released addCategory_NimbleSSH PropertySource for the following SSH-based LogicModules: Nimble_Array_Info, Nimble_HDD_Disks, Nimble_SSD_Disks, Nimble_Volume_Latency, and Nimble_Array_Properties (PropertySource).

  • Linux SSH – 1 DataSource, 1 PropertySource

    Updated the regex in the Linux_SSH_Filesystems DataSource to handle output split on multiple lines; added debug mode.

    Updated the Linux_SSH_Info PropertySource to use the actual hostname instead of its string representation to generate values for the auto.network.names property. This prevents invalid values from being set for the property due to DNS resolution issues.

  • LogicMonitor_Portal_Metrics – 1 DataSource

    Removed usages of the commons-codec library, to align with Collector versions 29.102 and higher.

  • Microsoft_Azure_BlobStorage – 1 DataSource

    Due to changes to the Azure Service Insights API, the collection interval for this DataSource has been increased to one hour. The previous one-minute interval was resulting in data collection issues caused by too-frequent polls of the API.

  • Microsoft_Azure_ExpressRouteCircuit – 1 DataSource

    Increased the data collection interval to five minutes to match Azure’s recently adjusted minimum allowed collection frequency. The previous one-minute interval was resulting in gaps in historical data.

  • Office365_MSOnline_AccountLicense – 1 DataSource

    Updated to support Microsoft Office 365 licensing SKU updates (see Microsoft documentation for a current listing of SKUs); added datapoints and graphs to track the total units.

    Important: There may be some historical data loss upon import due to instances being deleted and replaced with instances corresponding to the updated SKUs.

  • OSPF_Neighbors – 1 DataSource

    Changed the metric type of the neighborEvents datapoint from gauge to derive; added datapoint and graph for the retransmit queue length.

  • Palo Alto Firewall – 1 DataSource, 1 ConfigSource

    Fixed misleading description and alert message for the swap_pct_used datapoint found in the PaloAlto_FW_SystemResources DataSource.

    Removed log4j usage from the PaloAlto_FW_CLIConfigs due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher.

  • RabbitMQ Queue – 1 DataSource

    Updated wildvalue to exclude special characters in instance names.

    Important: This may result in historical data loss for existing instances with special characters in their names due to new instances being created with sanitized names.

  • snmpIf- – 1 DataSource

    Added StatusAlert complex datapoint similar to the datapoint already present in the snmp64_If- DataSource. Alerting has not been moved to the new datapoint to prevent instance-level alert rule changes. Note: An improved interfaces DataSource is targeted for release in an upcoming version.

  • Topology Mapping – 2 PropertySources, 3 TopologySources

    General updates to LogicMonitor’s topology-mapping-specific LogicModules include:

    • BGP_Topology TopologySource
      • Disabled BGP topology for Fortigate devices due to merging issues caused by the use of restricted and overlapping private IPs.
      • Includes the BGP peer address during edge discovery.
    • Networking_L2_snmpSwitch TopologySource.
      • Added support for shared namespaces, short OUIs (organizationally unique identifiers) for mapping some IBM devices, and OUIs for some Emulex and PCS equipment.
      • Made minor fix to account for devices that do not return 802.1Q bridge table entries over SNMP, as is the case for some HP Switches.
    • OSPF_Topology TopologySource
      • Disabled OSPF topology for Fortigate devices due to merging issues caused by the use of restricted and overlapping private IPs.
      • Included the OSPF neighbor id during edge discovery
    • addERI_BGP PropertySource
      • Disabled BGP topology for Fortigate devices due to merging issues caused by the use of restricted and overlapping private IPs.
    • addERI_OSPF PropertySource
      • Fixed external resource type for OSPF switches that were incorrectly classified as routers.
      • Disabled OSPF topology for Fortigate devices due to merging issues caused by the use of restricted and overlapping private IPs.
  • Viptela_System_Memory – 1 DataSource

    Added new SystemStatusMemTotal_KB datapoint for total system memory; updated memoryUtilization complex datapoint to account for total memory, buffers and cache.

  • VMware VCenter – 1 TopologySource

    Change: Added safe navigation to the VMware_vCenter_Topology TopologySource to resolve topology generation issues resulting from an unknown HA state.

  • WinVolumeUsage- – 1 DataSource

    Updated the Capacity Detail graph to scale by bytes rather than gigabytes.

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there are times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any data loss due to the name variation that LogicMonitor expressly adds. However, you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable the deprecated LogicModule after you have imported its replacement and verified that it is working as expected.

LogicModule Name/Type Replaced By Reason End of Support Date
LogicModules Deprecated in v.142
LM_Device_Count
(DataSource)
LogicMonitor_Portal_Metrics Uses a deprecated API. It is strongly recommended that this LogicModule be deleted and the replacement LogicModule be used. 10/26/2020
Arista_Switch_Storage
(DataSource)
Arista_Switch_FlashStorage

Arista_Switch_Memory

Arista_Switch_StorageUsage
The replacement DataSources filter out instances to allow for separate DataSource monitoring of memory, flash storage, and standard storage. 10/26/2020
LogicModules Previously Deprecated (over past five versions)
Windows_SNMP_Services
(DataSource)
N/A Windows SNMP support has been deprecated by Microsoft since Server 2012 R2. As a result, this DataSource does not collect reliable data for Server 2016 and above. 2020-12-02
Linux_SSH_CGroupStatus
(DataSource)
Linux_SSH_ServiceStatus Did not provide accurate/useful data and can be deleted; the existing Linux_SSH_ServiceStatus DataSource has been retooled in v.141 to perform the same function. 2020-09-18
Linux_SSH_NetworkTCPUDP
(DataSource)
Linux_SSH_TCPUDP The replacement DataSource offers several advantages including (1) the use of the more widely supported nstat (part of iproute2) command and netstat as fallback if nstat is not available and (2) additional monitoring for packet, datagram and error related metrics 2020-09-18
QNAP Volumes
(DataSource)
QNAP_Volumes Changed the collection method from standard SNMP to scripted SNMP to properly handle the units returned for the VolFreeSize and VolTotalSize datapoints. In the now-deprecated version, these datapoint calculations were failing if the returned values were not expressed as terabytes leading to data misrepresentation. 2020-09-18

Entering Beta

LogicMonitor is currently beta testing significant UI enhancements for the Alerts page. The new UI is more intuitive and efficient, featuring:

  • Increased data density
  • Faster loading times
  • More advanced filtering options

Any customer with a sandbox portal will be able to test drive these UI enhancements in their sandbox portal, targeted for roll out October 6 (subject to change). To access the new UI, open the Alerts page and add an “s” onto the very end of the URL (transforming “/alert” to “/alerts”).

Feedback on the new UI is welcome and can be submitted right through your portal, as outlined in Accessing Support Resources.

In this Article: