Support Center Home


v.137 Release

Published on 06.11.20

v.137 Highlights:

  • Platform Enhancements: LM Exchange, dashboard widgets, reports, alert integrations, and more
  • New and Updated Monitoring Coverage: Cisco Meraki, Cisco SD-WAN, Cisco UCS, Palo Alto, Pure Storage, and several AWS and Azure cloud resources
  • Looking Ahead: Collector MGD 28.005 auto-update, SiteMonitor IP address updates, elimination of percent() function use in complex datapoints

Platform Enhancements

Alerting

  • Improved alert filtering. The Cleared filter now works with the Anomaly filter (as found on both the Alerts page and the Alerts tab, which is available for a resource from the Resources page). This is useful for viewing cleared alerts for which notifications were not routed as a result of dynamic threshold evaluation.

Alert Integrations

  • Autotask integration. Previously, line breaks in Autotask XML ACTIVE payloads (URL endpoint .autotask.net/atservices/1.5/atws.asmx) were denoted by carriage returns ( ), which was resulting in poor formatting. Line breaks are now denoted by line feeds ( ) for proper description display. Regenerating the payload will generate the correct syntax.
  • Obfuscation of sensitive properties. Passwords and other sensitive custom properties (property names that end with special keywords such as .key, .pass, and .password) are no longer displayed in clear text within the Integrations Logs.

AppliesTo Scripting

  • AppliesTo test results. In v.136, we introduced a fix for an issue that was causing resources to be incorrectly omitted from AppliesTo test results if conditions were met via property inheritance. Because this fix turned out to only partially resolve the issue, we are releasing another fix in v.137 to resolve the issue in its entirety.

Audit Logs

  • Exclude operator. The exclude operator (!) was not working as expected when filtering by user in the Audit Logs and the Audit Log report. This issue has been fixed.

Dashboards

  • Website Status widget. Previously, when multiple testing locations existed for an individual website, forecasting data was not displayed correctly. This issue has been resolved.
  • Table widget. When configuring the Show color bars option for a dynamic table widget, the Minimum Value and Maximum Value fields are disabled if the Show Percentage option is not selected. This was done to avoid confusion as the color coding of datapoint values on a table widget is designed to only be used in conjunction with values represented by percentages.

LM Cloud

  • Improved handling of custom polling intervals. Previously, when custom polling intervals were created for cloud resources, portions of the impact were not handled correctly. With v.137, a change has been made that better supports custom polling intervals—and subsequent metrics graphing. Note: complex datapoints may still be incorrectly impacted by custom polling intervals.
  • Improved RBAC enforcement. Previously, users without LM Cloud permissions were able to add some services. This issue has been fixed.
  • AWS updates:
    • New region property. When used, the custom AWS.Region property overrides the AWS region (as set in the system.aws.region property) for calling the API. A hierarchy can be established with different regions specified at the instance, device, and account levels. This is useful for monitoring instances across multiple regions for a single resource. Example AWS services in which this custom property may be implemented include Elasticsearch and Connect, among others.
    • Improved service permission handling. LogicMonitor can now handle AWS service permissions more similarly to each other, providing for some reporting abilities even if we do not have explicit permissions to view tags on the service.
    • AWS CloudWatch Active Discovery method. An Active Discovery method for AWS CloudWatch was added. You may find this useful if creating multi-instance DataSources that pull custom CloudWatch metrics, and you want to be able to dynamically reference instances (disks).
    • AWS EC2 Scheduled Events. AWS EC2 Scheduled Events were alerting upon completion, which is an inappropriate alert condition. This has been fixed.
  • Microsoft Azure updates:
    • Azure backup jobs. Previously, larger Azure backup jobs were timing out in some cases when attempting to retrieve information. An update in retrieval methodology has been introduced to fix this issue and reduce the occurrence of timeouts.

LM Container

  • Namespace deletion. Namespaces deleted from monitored clusters weren’t being automatically removed from LogicMonitor. This issue has been fixed.

LM Exchange

  • Locator ID support. The LM Exchange interface now offers a Find Locator field that supports the input of the LM Locator ID. This field takes you directly to the detail screen of the corresponding LogicModule and restores the ability to import from LM Locator ID, which was briefly lost when the LM Exchange was enabled in v.136.
  • LogicModule sorting. Previously, sorting LogicModules in the Public Repository interface would cause some of them to be selected for install/upgrade. This issue has been fixed.

LM Intelligence

  • Enhanced account information transparency for intelligence features. Counts of root cause analysis rules and dynamic thresholds are now displayed in the Device Counts table (available under Settings | Account Information | Contacts), allowing you to quickly identify how extensively these intelligence features are used throughout your account.

NetFlow

  • Resolved error in unit labeling. NetFlow traffic volume, as displayed on the Traffic tab for a resource, is now correctly labeled as bits (and not octets).

Reports

  • SLA report. To improve the accuracy of calculated SLA values, the SLA report now takes into account the time lapsed until the date a server is provisioned.
  • User report. Special characters can now be used in the First Name and Last Name filters. Previously, entry of special characters was causing the resulting criterion to be prepended with additional special characters.

Security

  • Miscellaneous security fixes and improvements. Various security fixes and improvements are being released with this version.

Topology Mapping

  • Vertex details display. Clicking a vertex on a topology map now displays a table that features a fixed set of topology properties for the represented resource.

New and Updated Monitoring Coverage

Upon your account’s upgrade to v.137, import our new and updated LogicModules from the LogicMonitor public repository to expand and enhance your monitoring coverage.

New Monitoring Coverage

  • AWS Connect – 1 DataSource

    Added new datapoints.

  • AWS EBS Volume Snapshots – 1 DataSource

    Monitors EBS snapshot count and duration since the previous snapshot.

  • AWS EC2: Instance Type Service Limits (by Region) – 1 DataSource

    A new DataSource, named AWS_EC2_InstanceTypeServiceLimitsByRegion, has been released to properly pull the vCPU usage statistics for F, G, P, Inf, and Standard instance types.

    Note: Due to the nature of the changes and to prevent historical data loss, this new DataSource deprecates the AWS_EC2_ServiceLimits DataSource. To avoid unnecessary CloudWatch requests, we recommend you disable this deprecated DataSource.

  • AWS ECS Container Insights – 1 DataSource

    Gathers Amazon ECS container insights via CloudWatch.

  • AWS Elasticsearch: Data Nodes, Master Nodes – 2 DataSources

    Two new DataSources have been released that gather Elasticsearch cluster performance data for data nodes and individual master nodes (as reported by CloudWatch).

    As discussed in the Updated Monitoring Coverage section, the AWS_Elasticsearch_MasterNode DataSource, which gathers aggregated cluster performance data for master nodes, has been updated to better reflect its aggregation role within the context of the two new DataSources.

  • AWS S3 Glacier – 1 DataSource

    Monitors S3 Glacier vault size (as reported by Cloudwatch).

  • (Topology Mapping) BGP – 1 PropertySource, 1 TopologySource

    The addERI_BGP PropertySource and BGP_Topology TopologySource were released for expanded BGP topology mapping coverage.

  • (Topology Mapping) Cisco EIGRP – 1 PropertySource, 1 TopologySource

    Enhanced topology mapping coverage.

  • Cisco Meraki – 10 DataSources, 2 PropertySources, 1 TopologySource

    LogicMonitor has released a new monitoring suite for Cisco Meraki to address SNMP scaling issues that occur in large deployments.

    Note: As a result of this new monitoring suite, we have deprecated eight legacy Meraki DataSources. For details on migrating to this new monitoring suite, see Cisco Meraki Monitoring.

  • Cisco SD-WAN – 15 DataSources, 2 PropertySources, 1 TopologySource

    Monitors performance and availability metrics for various edge devices across your network. See Cisco SD-WAN Monitoring for setup details.

  • Cisco UCS – 7 DataSources

    Beginning with v.134, LogicMonitor has been releasing new monitoring for Cisco UCS that leverages the UCS Manager API (rather than relying on SNMP as the collection method). With v.137, we are releasing seven more DataSources to finalize our API coverage efforts: Cisco_UCS_BladeServerComponents, Cisco_UCS_FIStoragePartitions, Cisco_UCS_IOCards, Cisco_UCS_RackServerComponents, Cisco_UCS_ServiceProfiles, Cisco_UCS_VLANs, and Cisco_UCS_VSANs.

    With the release of these final seven DataSources, we have officially deprecated all of the legacy SNMP-based DataSources. For more details, see Cisco UCS Monitoring.

  • ISDN Channels – 1 DataSource,1 PropertySource

    A new DataSource named ISDN_Channels has been released to replace the now-deprecated ISDN Channels in use- DataSource. A new PropertySource has been released as well to more elegantly handle DataSource association via a system.categories property query.

  • Microsoft Azure App Service Environment Multi-Role Pools – 1 DataSource Monitors metrics for Azure App Service Environment multi-role pools, including active requests, average response time, bytes received/sent, CPU/memory percentage, and more.
  • (Topology Mapping) OSPF – 1 PropertySource, 1 TopologySource

    The addERI_OSPF PropertySource and OSPF_Topology TopologySource were released for expanded OSPF topology mapping coverage.

  • Palo Alto Firewall: IPSec Tunnels, GlobalProtect Sessions – 3 DataSources

    New monitoring for IPSec tunnels (overview and status data) and GlobalProtect active sessions (overview data) is available for Palo Alto firewalls.

  • Pure Storage – 2 DataSources, 3 PropertySources

    The PureStorage_Troubleshooter and PureStorage_VolumePerformance_API_v1_4 DataSources were added to this monitoring suite to enhance coverage. In addition, three new PropertySources were added to provide more granular control over DataSource association.

    Note: As discussed in the Updated Monitoring Coverage section, updates (and deprecations) were made to existing Pure Storage DataSources. See Pure Storage Monitoring for more information on configuring this monitoring suite.

  • SNMP Network Interfaces – 1 PropertySource

    A new PropertySource named SNMP_Interfaces_Mode has been released to determine if a device should be using 32-bit or 64-bit counters for the SNMP_Network_Interfaces DataSource. (As discussed in the Updated Monitoring Coverage section, the SNMP_Network_Interfaces DataSource has been updated to better support 32- and 64-bit counters.

  • SSL Certificates – 1 DataSource

    Released a new DataSource named SSL_Certificates that uses an embedded Groovy script for data collection. This new DataSource deprecates the legacy SSLCerts- DataSource.

Updated Monitoring Coverage

  • Arista EOS – 1 ConfigSource

    Configs can now optionally disable the ENABLE command.

  • Aruba Wireless Controller – 1 ConfigSource

    Performed a major rewrite to align with our newer ConfigSource template (which reduces code volume, increases execution efficiency, and offers other improvements).

  • AWS EC2 Service Limits – 1 DataSource (DEPRECATED)

    The AWS_EC2_ServiceLimits DataSource is now deprecated due to the release of a new DataSource (see New Monitoring Coverage section) that improves operations. Due to the scope of changes and to prevent historical data loss, deprecation (rather than a new version release) was necessary. To avoid unnecessary CloudWatch requests, we recommend you disable this deprecated DataSource.

  • AWS Elasticsearch: Master Node – 1 DataSource

    As discussed in the New Monitoring Coverage section, two new DataSources have been released that gather Elasticsearch cluster performance data for data nodes and individual master nodes (as reported by CloudWatch).

    To better reflect its role within this context, the description for the AWS_Elasticsearch_MasterNode DataSource, which gathers aggregated cluster performance data for master nodes, has been updated to better reflect its aggregation role within the context of these two new DataSources.

  • AWS MSK – All 3 DataSources

    Updated datapoint calculations to use default aggregators instead of hard-coded averages.

  • AWS Service Health – 1 EventSource

    Updated description and technical notes.

  • Cisco Memory – 1 DataSource

    Removed incorrectly set token in alert message.

  • Cisco Meraki – 8 DataSources (DEPRECATED)

    As discussed in the New Monitoring Coverage section, LogicMonitor has released a new monitoring suite for Cisco Meraki to address SNMP scaling issues that occur in large deployments. As a result of this new monitoring suite, we have deprecated eight legacy Meraki DataSources. For details on which DataSources have been deprecated, see Cisco Meraki Monitoring.

  • Cisco NTP – 1 DataSource, 1 PropertySource

    Added compatibility for NX-OS

  • Cisco UCS – 13 DataSources (DEPRECATED)

    Beginning with v.134, LogicMonitor has been releasing new monitoring for Cisco UCS that leverages the UCS Manager API (rather than relying on SNMP as the collection method). As discussed in the New Monitoring Coverage section, with v.137, we now have complete monitoring coverage via API. Therefore, we are officially deprecating all legacy SNMP-based DataSources. For more details, see Cisco UCS Monitoring.

  • Dell Networking – 1 ConfigSource

    Performed a major rewrite to align with our newer ConfigSource template (which reduces code volume, increases execution efficiency, and offers other improvements).

  • EMC Isilon – 1 PropertySource

    Replaces SNMP SysOID Map for better matching (prevents OID matching on pfSense devices).

  • EMC LUN NavisSEC CLI – 1 DataSource

    Updated data collection script to replace % in output during post processing.

  • EMC VNXe – 10 DataSources, 1 PropertySource (entire monitoring suite)

    Added missing alert thresholds and keyword tags.

  • Fujitsu Eternus (Controller Modules, RAID Groups, Volumes) – 3 DataSources

    Added regex prompt matching for various Eternus system types; cleaned up code

  • HP MSA – 3 Datasources

    Updated the Technical Notes fields for the HP_MSA_Disks, HP_MSA_VirtualDisks, and HP_MSA_Volumes DataSources to document the properties required for these DataSources to successfully associate with relevant devices. For more information on configuring this monitoring suite, see HP MSA / StorageWorks / P2000 Monitoring.

  • HPE Network Config – 1 ConfigSource

    Added missing get_display_commands() method; updated Technical Notes field.

  • Kubernetes Pod – 1 DataSource

    Updated the collection script to look for pod IP if host IP isn’t present.

  • Linux SSH CPU/Memory – 1 DataSource

    Added a new complex datapoint and graph for memory utilization.

  • Microsoft Azure: Application Gateway – 1 DataSource

    Added new available metrics.

  • Microsoft Azure: Firewall – 1 DataSource

    Added new available metrics.

  • Microsoft Azure: VMs – 1 DataSource

    Removed colon from display name.

  • Microsoft Office 365: Exchange Online Users – 1 ConfigSource (REMOVED)

    Due to the creation of excessive instances, the Office365_ExchangeOnline_Users ConfigSource has been removed from the LogicMonitor public repository.

  • Microsoft Office 365 Reports: Yammer Device Usage – 1 DataSource

    Updated datapoint collection script to default to -1 if No Data was returned.

  • NetApp: 7 Mode Aggregates, Cluster Aggregates – 2 DataSources, 2 TopologySources

    Unlinked topology dependency from LUN for basic edges.

  • NetSNMP CPU with Cores – 1 DataSource

    Performed minor graph fixes; cleaned up various datapoint descriptions and alert messages.

  • Nimble Volume Latency – 1 DataSource

    Updated regex; cleaned up graphs, datapoints, and alert messages.

  • Oracle – 19 DataSources, 3 PropertySources (entire monitoring suite)

    Applied a minor fix to pass non-default port values as integers (previously passed as strings causing errors).

  • OSPF_Neighbors – 1 DataSource

    Added null checks to contextNames.

  • PaloAlto Firewall: Global Counters – 1 DataSource

    Updated the appliesTo statement to additionally require that an API key be present in order for the DataSource to associate; cleaned up graphs.

  • PowerShell-based LogicModules – 14 DataSources, 3 PropertySources, 1 TopologySource

    For the following PowerShell-based LogicModules, scripts were updated to use -match instead of -like.

    DataSources:

    • Citrix All Licenses
    • CPU
    • HyperV Hypervisor Stats: 2008, 2008r2, 2012, 2016
    • Microsoft DHCP: IPv4 Scopes, Servers
    • VMware Horizon PColP Sessions
    • Virtual Machines
    • Virtual Network Adapter
    • Virtual Storage
    • Virtual Switches
    • Virtual Switch Ports

    PropertySources:

    • addCategory: Microsoft Exchange PowerShell, Windows Failover Cluster, Microsoft PowerShell Info

    TopologySources:

    • HyperV
  • Pure Storage – All 11 existing DataSources (9 updated, 2 DEPRECATED)

    Updated the appliesTo statement to additionally require the presence of “PureStorage” as a system.categories value (previously only the presence of an API token was required). DEPRECATED the PureStorage_ArrayInfo (its function now replaced by a new PropertySource of the same name) and the PureStorage_SnapshotReplication (the data returned by this DataSource was intermittent and therefore not beneficial) DataSources.

    Note: As discussed in the New Monitoring Coverage section, there were also several new LogicModules released for Pure Storage. See Pure Storage Monitoring for more information on configuring this monitoring suite.

  • SNMP Network Interfaces – 1 DataSource

    Updated to better support 32- and 64-bit counters. (As discussed in the Updated Monitoring Coverage section, a new PropertySource named SNMP_Interfaces_Mode has been released to determine if a device should be using 32-bit or 64-bit counters for this DataSource.)

  • Added NetFlow interface alert threshold compatibility.
  • Sonicwall SonicOS Config – 1 ConfigSource

    Expanded regex prompt matching.

  • StatusPageIO – 1 PropertySource

    The addCategory_StatusPageIO_Key PropertySource now applies to resources that have a value of “statuspage” set for their system.categories properties to allow for you to manually associate a device.

  • (Topology Mapping) PropertySources – 1 PropertySource

    Updated the addERI_Windows PropertySource to check for HyperV resources.

  • (Topology Mapping) TopologySources – All 24 TopologySources

    Update to TopologySource grouping for all TopologySources.

    Updated the Networking_L2_snmpSwitch TopologySource for post processing of Microchip MACs (ignoring them if paired with another MAC and linking to other MAC instead).

  • Veeam Backup & Replication – 1 DataSource, 1 PropertySource

    Updated the Veeam_BackupAndReplication_BackupSessions DataSource and addCategory_Veeam_BackupAndReplication_PowerShell PropertySource to bring the Veeam Backup & Replication monitoring suite into compatibility with version 10.

  • VMware vCenter: Admission Control – 1 DataSource

    Removed upper limits for the failoverLevelDifference datapoint; added Groovy safe navigation.

  • VMware vCenter: Datastore Performance – 1 DataSource

    Fixed duplicate datapoint descriptions shared by ReadKBytesperSec and ReadCommands.

  • VMware vCenter: Host Interfaces, Host Performance – 2 DataSources

    Update to use ##POLLINTERVAL## to scale according to the configured collection interval.

  • VMware vCenter VM Status – 1 DataSource

    Fixed typo in Active Discovery script that was causing error.

  • Windows Cluster Node State – 1 DataSource

    Added missing datapoint descriptions.

  • Zoom: Service Status – 1 DataSource

    Updated the expression for the Status datapoint’s alert threshold from > 1 2 3 to >= 1 2 3 to ensure alerting occurs for deprecated (1) service status; updated alert message.

Looking Ahead

Collectors

  • Collector MGD 28.005 auto-upgrade. LogicMonitor has designated the general deployment Collector version of GD 28.005, released in March, as the next MGD (minimum general deployment) Collector version. On June 30, between 6 and 9 p.m. PT, all Collectors in your LogicMonitor platform below version GD 28.005 will be automatically updated to this new minimum version (we encourage you to upgrade on your own schedule prior to the automatic update). After June 30, we will officially deprecate and stop supporting the previous minimum general deployment of MGD 27.005. For more details, see MGD Collector – 28.005.

Datapoints

  • Elimination of percent() function use in complex datapoints. In an upcoming release, LogicMonitor intends to add validation for the purpose of preventing the use of the percent() function within complex datapoint expressions. This function is intended to produce a percentile value, but requires data for multiple timestamps to do this. As such, it only works properly in virtual datapoints and its use within complex datapoints introduces ambiguity. As part of this initiative, we will also remove any existing complex datapoints that reference this method to ensure continuity in existing DataSource functionality.

    Note: If you are using this function in the snmp64_If- DataSource, we recommend updating to the latest SNMP_Network_Interfaces DataSource (released in v.136), which uses Groovy to automatically handle this logic outside of complex datapoints.

Website Monitoring

  • Originating IP address updates for SiteMonitor. Over the next several weeks, LogicMonitor intends to update the originating IP addresses for our SiteMonitor service, which consists of external testing locations used for Web Checks and Ping Checks. All potential IP addresses are listed in LogicMonitor’s External Testing Locations. Please ensure that your network’s firewall(s) permits access to all IP addresses on this list in order to maintain continued service.

In This Article