Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
Over the past few months, LogicMonitor has been beta testing an enhanced alert integration for Slack that leverages a brand new LogicMonitor app for Slack. On September 24, this improved integration is slated for general availability (subject to change due to the dynamic nature of the Slack app review process).
This new out-of-the-box alert integration between LogicMonitor and Slack is bi-directional, supporting the ability to:
To learn more about the new Slack integration, see Slack Integration.
LogicMonitor’s network traffic monitoring capabilities now include support for the NBAR2 protocol. The addition of NBAR2 nicely rounds out LogicMonitor’s suite of supported network traffic protocols which also includes NetFlow, JFLOW, sFlow, and IPFIX.
NBAR2 is the next generation of Cisco’s NBAR (network based application recognition) protocol, which recognizes and classifies network traffic by protocol or application. LogicMonitor’s support of NBAR2 allows you to:
Although network traffic monitoring capabilities are available in all LogicMonitor portals, the ability to collect NBAR2 data will be available to users of LogicMonitor Enterprise only. Users of LogicMonitor Professional will have trial access to the feature through October 5 2020.
NBAR2 functionality requires Collector version 29.101 or greater. For more information on LogicMonitor’s network traffic monitoring capabilities, see Network Traffic Monitoring.
Upon your account’s upgrade to v.141, import our new and updated LogicModules from the LogicMonitor public repository to expand and enhance your monitoring coverage.
A new DataSource named AWS_Elemental_MediaPackage_VOD has been added to monitor throughput, request count, and response time metrics for MediaPackage VOD packages.
Alerts on AWS Trusted Advisor checks.
A new DataSource named Linux_SSH_TCPUDP has been released to replace Linux_SSH_NetworkTCPUDP. See Deprecated LogicModules for details.
Added a new DataSource named Oracle_Database_WinServices to the Oracle monitoring suite that monitors the status of the Windows Services associated with an Oracle database.
A new DataSource named QNAP_Volumes has been released to replace QNAP Volumes. See Deprecated LogicModules for details.
The RD_Gateway_Connections DataSource and addCategory_RD_Gateway PropertySource work together to track the number of users currently connected via a Remote Desktop Gateway server.
Note: The release of these LogicModules is part of LogicMonitor’s initiative to enhance monitoring of the various remote work from home technologies that have become critical during this time. See Quick Reference for Remote Tools Monitoring for a list of remote tools monitoring capabilities our customers have found most helpful over the past few months.)
Expanded Viptela monitoring to gather metrics for tunnel status and color; SFP presence; and interface metrics including utilization, throughput and errors.
Updated several LogicModules in the Cisco Meraki monitoring suite to address merging issues between Meraki cloud and standard networking topologies: Cisco_Meraki_AccessPoints, Cisco_Meraki_Gateways, Cisco_Meraki_SecurityAppliances, Cisco_Meraki_Switches, and Meraki_Cloud_Topology (TopologySource).
The addERI_Device PropertySource, although not directly a member of the Cisco Meraki suite, was also updated for the same purpose.
Corrected the OID being used by the LatestRttStatus datapoint.
The collection scripts for the following DataSources were not collecting data for discovered instances: CommVault_Job_Subclients, CommVault_Job_VMwareSubclients, and CommVault_Job_VMwareSubclientVMs. This has been fixed.
Note: For the CommVault_Job_VMwareSubclients DataSource, new instances will be generated, effectively breaking history with its previous set of instances; however, since data was never collected for the previous instances, this should be of no consequence to your operations.
Fixed incorrect time offset calculation when reporting events; shortened script; converted base64/gz-encoded string back to plain text.
Updated the Linux_SSH_CGroups and Linux_SSH_ServiceStatus DataSources, both of which install with Active Discovery disabled in order to prevent the production of many instances, to improve the process (and documentation) for instance discovery.
Fixed incorrectly ordered status codes in the DATABASESTATE datapoint’s description.
Invalid characters in instance names are now replaced with underscores to resolve collection/Active Discovery issues for the following DataSources: Microsoft_SQLServer_Databases, Microsoft_SQLServer_GlobalPerformance, and Microsoft_SQLServer_SystemJobs.
Updated the addCategory_MySQL PropertySource script to use Expect instead of sockets for improved discovery reliability.
Updated the addERI_OSPF PropertySource and OSPF_Topology TopologySource to fix ERI mismatch and improve flexibility of area ID discovery during topology map generation.
Added a new available_mem datapoint for version 9 CLI of Palo Alto firewalls; with this change, the swap_cached datapoint is no longer relevant and will report “NA”.
Updated all LogicModules in the Pure Storage monitoring suite that collect data via API query (the majority of LogicModules) to default to accessing the highest available version of the 1.x API due to stability issues with the 2.x API.
Removed additional decoration information from the sent request.
Corrected the description in place for the DiskWriteKbytesPerSec datapoint; performed minor cleanup for other datapoint descriptions.
Updated technical notes for Windows_SNMP_Memory and Windows_SNMP_Volumes DataSources to reference deprecation of SNMP on Windows. (These DataSources are currently operational if SNMP is enabled, but will be deprecated once Microsoft officially drops SNMP support).
The ApplesTo statement was accidentally reverted in a previously published version of this EventSource. This has been corrected and the EventSource no longer applies to Windows clusters.
Removed the alert threshold from the SplitIOPercent datapoint; added missing datapoint descriptions and graphs across all datapoints.
Made discovery and deny listing improvements to the addERI_Device PropertySource and Networking_L2_snmpSwitch TopologySource to enhance basic networking topology operations.
LogicMonitor deprecates LogicModules for a variety of reasons. Most common, it is because we have published a replacement LogicModule that provides superior access to the monitored technology. For example, the replacement supports more versions of the technology or provides improved scalability.
However, there are times when a LogicModule is deprecated with no replacement. For example, a LogicModule may not be replaced if the 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.
LogicMonitor is currently beta testing significant UI enhancements for the Alerts page. The new UI is more intuitive and efficient, featuring:
Any customer with a sandbox portal will be able to test drive these UI enhancements in their sandbox portal, targeted for roll out in mid October (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