v.134 Release: SAML SLO Support; New Monitoring for Cisco Wireless, Slack, and Public Cloud

Platform Enhancements

Alerting

• Formatting improvements for graphs included in email alerts. Formatting improvements have been made to the DataSource graphs included in email alert notifications to make the graphs more readable and more consistent with their display in the LogicMonitor interface.
• Resolving ##MESSAGE## token in EventSource alerts. Certain characters were resulting in the ##MESSAGE## token not populating properly for EventSource alert messages. This has been fixed.

LM Service Insight

• Character limit increase for adding individual instances into a Service. The character limit for resources that are members of Services has been increased from 24,000 to 50,000. This update is designed to further facilitate the creation of Services with many grouped instances (as member instances are stored as a single string in the predef.bizservice.members property).

Reports

• Resource Inventory report. The date format in place for displaying resource created-on dates and times was not property set, leading to the display of incorrect values. This issue has been corrected.

Security

• SAML Single Logout (SLO) support. LogicMonitor’s Single Sign-On (SSO) integration now includes support for the SAML Single Logout (SLO) protocol. Previously, a logout initiated from the LogicMonitor portal would sign out a user from LogicMonitor only, and not affect any other SSO applications with sessions initiated by the Identity Provider (IdP). If enabled, this new SLO functionality will trigger the IdP to additionally initiate a logout of every other SSO application to which that user has signed in. Administrators (and others with full access to manage account settings) can enable SLO functionality from the Single Sign On configuration settings (available by navigating to Settings | Single Sign On).

  Note: SLO has been implemented in accordance with the SAML v2 specification. Although functionality has been validated with several standards-based IdPs, we cannot guarantee compatibility with all IdPs as some don’t support the SAML specification in its entirety.

• Removal of session IDs. As noted in v.133 release notes, Session IDs have been removed from audit log entries (as displayed on the Audit Logs page) and corresponding API endpoints.
• Miscellaneous security fixes and improvements. Various security fixes and improvements are being released with this version.

Topology Mapping

• Improved map display. Topology map display has been improved to prevent resource labels from overlapping one another. When not in focus, resource labels are truncated to prevent overlap; the full label displays upon mouse hover.
• Alert routing suppressed icon included in map display. Topology maps now display the alert routing suppressed icon shown on the Alerts page for alert notifications that were disabled due to LogicMonitor’s root cause analysis or dynamic thresholds AIOps features. Non-suppressed alerts take precedence for the resource alert icon overlay. All alerts, including those with suppressed routing, are displayed in the alert list window.

New and Updated Monitoring Coverage

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

New Monitoring Coverage

• AWS CodeBuild – 1 DataSource
  • Discovers and monitors CloudWatch metrics for AWS CodeBuild projects, including build count, build status, and built time.
• AWS MQ StandbyBroker – 1 DataSource
  • Monitors Amazon MQ Standby Broker performance data, as reported by CloudWatch.
• AWS Route 53 Resolver – 1 DataSource
  • Discovers and monitors resolver metrics from CloudWatch for AWS Route 53 Resolver.
• AWS SageMaker – 1 DataSource
  • Discovers and monitors CloudWatch metrics for SageMaker endpoints, including memory utilization, invocations, and GPU data.
• Cisco Adaptive Security Virtual Appliance (ASAv) – 1 SNMP SysOID Map
  • New sysOID for Cisco ASAv.
• Cisco UCS – 7 DataSources, 1 PropertySource
  • LogicMonitor has released a new monitoring package for Cisco UCS that leverages the UCS Manager API (rather than relying on SNMP as the collection method). API data collection offers several advantages, including access to more data, less resource use which in turn allows for data to be collected at more frequent intervals, and easier setup. For more information on setting up this new Cisco UCS monitoring package, see Cisco UCS Monitoring.

    Note: These new DataSources overlap some (but not all) functionality of the existing SNMP-based Cisco UCS DataSources. For now, we are recommending that you do not disable the SNMP-based DataSources, but rather run both sets in parallel. In an upcoming release, we will be expanding the reach of the API-based suite and will, at that time, note any official DataSource deprecations.

• Cisco Wireless Controller (WLC) – 12 DataSources, 1 PropertySource
  • LogicMonitor’s existing Cisco WLC monitoring is significantly enhanced with the release of 12 new DataSources (and one PropertySource). For details, see Cisco Wireless Monitoring.

    Note: These new DataSources deprecate several existing DataSources. For details on which DataSources are deprecated and tips on migrating, see Cisco Wireless Monitoring.

    Note: Minor updates are available for the existing Cisco_Wireless_AP DataSource, which is also a member of this suite.

• GCP AI Platform Jobs – 1 DataSource
  • Discovers and monitors StackDriver data for GCP AI Platform jobs, including CPU and memory utilizations and bytes sent and received.
• GCP Cloud Composer – 1 DataSource
  • Discovers and monitors StackDriver data for GCP Cloud Composer, including API requests and latency.
• GCP DataFlow – 1 DataSource
  • Discovers and monitors StackDriver data for GCP DataFlow, including billable shuffle, current vCPUs, shuffle slots, and time.
• GCP Firestore – 1 DataSource
  • Discovers and monitors StackDriver data for GCP Firestore, including disk usage percent and disk IO time OOTB.
• GCP IoT – 1 DataSource
  • Discovers and monitors StackDriver data for GCP IoT, including billable bytes, connected devices, and more.
• Hyper-V – 2 DataSources, 1 PropertySource, 1 TopologySource
  • For improved topology support, the following Hyper-V LogicModules have been created: Win_HyperV_VirtualStorage and Win_HyperV_VirtualSwitches (DataSources); addERI_HyperV (PropertySource); and HyperV_Topology (TopologySource).

    Note: The new Win_HyperV_VirtualStorage DataSource serves to deprecate the Win2k12_HyperV_VirtualStorage and Win2k12r2_HyperV_VirtualStorage DataSources. If you are currently running these now-deprecated DataSources, you will not experience any data loss upon importing the new DataSource because of the name variation. However, you will collect duplicate data and potentially receive duplicate alerts for as long as all three DataSources are active. For this reason, we recommend that you disable the legacy DataSources after you have imported the new DataSource and verified that it is working as expected.

• Microsoft Azure Cognitive Search – 1 DataSource
  • Discovers and monitors Azure Monitor metrics for Azure Cognitive Search.
• Microsoft Azure Key Vault – 1 DataSource
  • Discovers and monitors Azure Monitor metrics for Azure Key Vault, including availability, saturation, and API statistics.
• Microsoft Azure Notification Hubs – 1 DataSource
  • Discovers and monitors Azure Monitor metrics for Azure Notification Hubs, allowing monitoring of push notifications, including scheduled, registration, incoming and outgoing metrics.
• Microsoft Azure Relay – 1 DataSource
  • Discovers and monitors Azure Monitor metrics for Azure Relay, including sender, listener, and connection data.
• Microsoft SQL Server – 1 PropertySource
  • A new PropertySource named Microsoft_SQLServer_SQLAuthConnections has been added to the SQL Server monitoring suite in order to allow for SQL Authentication connections to work when Integrated Authentication attempts result in a Collector timeout.
• Slack Status – 1 DataSource, 1 EventSource, 1 PropertySource
  • Leverages the Slack Status API to monitor and alert on incident, outage, and maintenance events for the various Slack services. See Slack Status Monitoring for details on what this package monitors, as well as instructions for setting up monitoring.
• Synology – 1 PropertySource
  • The addCategory_Synology PropertySource has been added to enable auto-detection and categorization of Synology NAS resources. These resources run on Linux and, previously, were detected and categorized as Linux servers only.
• Unomaly – 1 DataSource, 3 EventSources, 1 PropertySource
  • Displays log anomalies and knowns collected by Unomaly and monitors the frequencies of these events over time. See Unomaly Monitoring for details.

Updated Monitoring Coverage

• AWS Elasticsearch – 1 DataSource
  • Fixed issue in the utilization expression in place for the “ClusterUsedSpacePercent” datapoint to properly calculate 0-100%.
• AWS MQ Broker – 1 DataSource
  • Updated all datapoint expressions for split between Active/HA brokers (partnered with new Standby Broker DataSource)
• Cisco AIP SSM Memory Pools & Cisco Nexus CPU and Memory – 2 DataSources
  • Updated datapoint OIDs to use newer 64-bit counters for better reporting of memory values that are over 32-bit maximum; performed cleanup on various datapoint descriptions and graphs.
• Cisco ASA – 1 SNMP SysOID Map
  • Extended coverage for Cisco ASA 5506 and 5516.
• Cisco FRU Power – 1 DataSource
  • Replaced the complex datapoint, which was used exclusively for alerting, with expanded alerting across the existing normal datapoints.
• Cisco IPSec Tunnels – 1 DataSource
  • Updated datapoint and graph labeling to reference “bps” (bits per second) instead of “bytes per second”; performed minor graph cleanup.
• Cisco UCS – Legacy DataSources (Deprecated)
  • As discussed in the previous section, LogicMonitor has released a new monitoring package for Cisco UCS, which effectively serves to deprecate existing Cisco UCS DataSources. (The new DataSources feature underscores in their names whereas the legacy DataSources do not).

    Note: If you are currently using the now-deprecated DataSources, you will not experience any data loss upon importing the new DataSources because of this name variation. However, you will collect duplicate data and potentially receive duplicate alerts for as long as both DataSources are active. For this reason, we recommend that you disable the legacy DataSources after you have imported the new ones and verified that they are working as expected. For more information on migrating to the new Cisco UCS monitoring package, see Cisco UCS Monitoring.

• Cisco Wireless Access Points – 1 DataSource
  • Added graphs; updated datapoint descriptions; instance-level grouping enabled for access points.

    Note: As discussed in the previous section, LogicMonitor has significantly enhanced Cisco wireless (WLC) monitoring with the addition of 12 new DataSources. This DataSource is a part of that monitoring suite.

• (Topology Mapping) Cisco Wireless – 1 PropertySource, 1 TopologySource
  • The addERI_Cisco PropertySource and Cisco_Wireless TopologySource have been updated to block MAC ERI settings on the controller, as well as add edge connections from the controller to the AP.
• Huawei – 1 DataSource, 1 PropertySource
  • Instance-level grouping has been removed from the Huawei_Chassis_SystemStats DataSource; the addCategory_Huawei PropertySource is targeting a different OID for improved resource matching.
• Hyper-V – 2 DataSources (Deprecated)
  • As mentioned in the previous section, two new Hyper-V DataSources have been created to better support topology mapping: Win_HyperV_VirtualStorage and Win_HyperV_VirtualSwitches. The new Win_HyperV_VirtualStorage DataSource serves to deprecate the Win2k12_HyperV_VirtualStorage and Win2k12r2_HyperV_VirtualStorage DataSources.

    If you are currently running these now-deprecated DataSources, you will not experience any data loss upon importing the new DataSource because of the name variation. However, you will collect duplicate data and potentially receive duplicate alerts for as long as all three DataSources are active. For this reason, we recommend that you disable these legacy DataSources after you have imported the new DataSource and verified that it is working as expected.

• Juniper SA Statistics – 1 DataSource
  • Updated datapoint descriptions and graphs; changed the DataSource display name to “Pulse Secure / Juniper SA statistics” (and updated description to reference Pulse Secure as well).
• Microsoft DHCP IPv4 Scopes – 1 DataSource
  • Fixed an issue in the Active Discovery script that was preventing instances from being discovered.
• Microsoft DHCP IPv4 Servers – 1 DataSource
  • To prevent old instances from lingering, the Automatically Delete Instance option is now checked for the DataSource definition’s Active Discovery configurations (this option removes instances from the Resources tree when Active Discovery determines that an instance no longer exists); performed minor cleanup on requests graph.
• Microsoft Exchange Mailbox Overview 2016+ – 1 DataSource
  • Across majority of datapoints, fixed the datapoint key to reference ##WILDVALUE## instead of ##WILDALIAS##; this issue was resulting in No Data being returned for datapoints.
• Microsoft Office 365 – 7 DataSources, 1 PropertySource, 1 ConfigSource
  • Updated the PowerShell script to better handle special characters that may be present in resource hostnames and password values for the following LogicModules: Office365_ExchangeOnline_MailboxStatistics, Office365_MSOnline_AccountLicense, Office365_Reports_MicrosoftTeamsUserActivity, Office365_Reports_OneDriveFileCounts, Office365_Reports_OutlookEmailActivity, Office365_Reports_UserActivityDetails, Office365_SharepointOnline_SiteStatus, addCategory_Office365 (PropertySource), and Office365_SharepointOnline_TenantConfig (ConfigSource).
• Microsoft Office 365 SharePoint Online Site Status – 1 DataSource
  • Updated the AppliesTo field to reference the correct resource property. Specifically, the logic was changed from hasCategory("Office365") && spoadminsite to hasCategory("Office365") && office365.spoadminsite.
• Microsoft SQL Server – 1 PropertySource
  • As discussed in the previous section, a new PropertySource named Microsoft_SQLServer_SQLAuthConnections has been added to the SQL Server monitoring suite in order to allow for SQL Authentication connections to work when Integrated Authentication attempts result in a Collector timeout. As part of this effort, the SQL Authentication functionality was removed from the existing Microsoft_SQLServer_Connections PropertySource and placed into the new PropertySource.
• Microsoft SQL Server Troubleshooter – 1 DataSource
  • Fixed a typo in the alert message.
• NetApp Cluster Status – 1 DataSource
  • The collection script wasn’t previously associating “broken” container types with the “brokenDisks” datapoint; the script has been updated to include this container type status in the datapoint’s count of failed disks.
• NetSNMP Memory Usage – 1 DataSource
  • Corrected the description in the Technical Notes field of the DataSource definition to reference “NetSNMPMem” as the name of the DataSource being replaced rather than the previous incorrect reference of “NetSNMPMem-“.
• Synology RAID Status – 1 DataSource
  • Due to an unstable SNMP agent on Synology hosts, static alert thresholds have been removed from datapoints so as to not generate false alerting.
• Veeam Backup & Replication – 10 DataSources
  • Added support in the collection script for multiple versions of PowerShell for the following 10 Veeam Backup & Replication DataSources: Veeam_BackupAndReplication_BackupSessions, Veeam_BackupAndReplication_Jobs_Backups, Veeam_BackupAndReplication_Jobs_BackupSync, Veeam_BackupAndReplication_Jobs_ConfigBackup, Veeam_BackupAndReplication_Jobs_Copy, Veeam_BackupAndReplication_Jobs_ManagedAgentBackups, Veeam_BackupAndReplication_Jobs_Replicas, Veeam_BackupAndReplication_Jobs_SureBackups, Veeam_BackupAndReplication_Jobs_VMWareSureBackups, and Veeam_BackupAndReplication_VMwareProxyServers.
• (Topology Mapping) VMware vCenter – 1 TopologySource
  • A flag for virtual port/switch and bridging interface data has been added to the VMware_vCenter_Topology TopologySource.
• VMware VCSA Filesystem Capacity – 1 DataSource
  • Added an Active Discovery filter to exclude archives from being discovered as instances. Because these filesystems often operate at 100% capacity by design, they were causing erroneous alerts.
• VMware VCSA Services – 1 DataSource
  • Enhanced messaging in the Technical Notes field of the DataSource definition to better inform customers that alerts are not enabled by default (due to some services consistently being in a stopped state) and that datapoint thresholds should be set per instance depending upon the needs of your unique environment.
• VMware vSphere VM Performance – 1 DataSource
  • Updated the “CPUReadyperVCPUPercent” datapoint calculation to use an auto-assigned property (auto.hardware.num_cpu) when determining CPU ready percentage per VCPU.
• WatchGuard IPSec Tunnels – 1 DataSource
  • Added support for SNMP v3.
• Zoom – 5 (All) DataSources
  • The page_size parameter was fine-tuned across all Zoom DataSources; for the Zoom_User_Stats DataSource, which was sometimes incorrectly returning No Data, the token expiry was additionally updated to 180 seconds (default Collector timeout) and small (75ms) wait between /user page calls was added to avoid hitting the rate limiter.