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!
LogicMonitor is releasing significant UI enhancements for the Alerts page. The new UI is more intuitive and efficient, featuring:
While the capabilities of the new Alerts page UI are largely parallel to those of the previous UI, some new functionality is being introduced, including:
When viewing the details of an alert, the new UI provides an at-a-glance sparkline for the datapoint in alert and brings alert notations front and center. In addition, as highlighted here, it provides options for maximizing the display of alert details, allowing you to “Expand” the alert detail pane upwards to fill more of the Alerts page screen or, for unobstructed viewing, to link to a new page that displays a maximized view of the alert detail pane.
Note: Upon deployment of the new UI, the left-hand Alerts navigation menu will automatically open the new Alerts page. However, you can still access the prior version of the Alerts page by removing the “s” from the very end of the Alerts page URL (transforming “/alerts” to “/alert”). The prior version of the Alerts page will remain available through at least version v.144.
For more information on using the new UI, see Managing Alerts from the Alerts Page.
The left-hand navigation menu features a new Profile menu. Only available when viewing areas of the product with version 4.x of the UI (currently the Alerts and Exchange pages), this menu is unique per user, allowing you to manage your user account, access support/training, configure various appearance settings, and log out.
Note: When viewing areas of the product with version 3 of the UI, you can find these options (manage user account, access support/training, log out) in the upper right corner of the platform header.
Upon rollout of this enhancement, any existing dynamic threshold configurations will update to having both the “Suppress notification within the band” and “Trigger alerts when” options checked to ensure no changes to expected current behavior.
(<existing AppliesTo statement>) || dummy.property == xyz
After saving the new statement and waiting a few moments, revert the AppliesTo back to its original statement and save once again.
“Note: To avoid circular references, the criteria that determines which devices are auto-assigned to a dynamic group (i.e. the AppliesTo script) can only evaluate properties of the host itself, not any inherited properties from those groups of which it is a member.”
“The highlighted devices are not being monitored by their preferred collector/group. To change the preferred collector or to perform failback, go to Collector Settings. In case of a device being monitored by an ABCG, check if the device has been moved to other group.”
Note: When viewing areas of the product with version 3 of the UI, remote support status displays in the upper right of the platform header.
Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.
Monitors AWS Elemental MediaConvert job output duration, errors, and transcoding/standby time.
Replacing the SNMP-based Cisco AIP SSM Memory Pools DataSource, this new DataSource offers a scripted SNMP version that returns accurate values. If you were previously using the now-deprecated DataSource, it can be deleted as it was providing invalid data.
The \.1\.3\.6\.1\.4\.1\.9\.1\.2406 SNMP SysOID Map applies Cisco_ASA_* LogicModules to Firepower 2130 devices.
Monitors metrics related to storage, clusters, nodes, consumers, hardware, and data protection for your Cohesity platform. For setup and monitoring details, see Cohesity DataProtect and DataPlatform Monitoring.
Gathers metrics for VeloCloud edge health, throughput, performance, and errors via the VeloCloud Orchestrator API. Also gathers system CPU and memory metrics via SNMP. For setup and monitoring details, see VMware VeloCloud Monitoring.
Updated to no longer fail to collect data on devices that have a license expiration date set to “N/A”.
Updated the metric type of the CurICASessions datapoint from derive to gauge.
The scripted DataSources in the HPA monitoring suite have been updated to improve handling of leading 0s in the authentication hash.
Changed the metric types of all datapoints from counter to derive.
The Microsoft_SQLServer_SQLAuthConnections and Microsoft_SQLServer_Connections PropertySources now include the loginTimeout parameter in JDBC strings to resolve high CPU usage on Collector v29.003 caused by the PropertySource script not timing out correctly.
The addCategory_NetApp and addCategory_NetApp_ESeries PropertySources now assign the category of “NetApp” to the system.categories property from API-based PropertySources rather than relying only on sysOIDs.
Updated the appliesTo function to associate with F5 devices.
A value of NoData (rather than -1) is now returned for metrics that are not returned by the array.
This LogicModule now accepts the property paloalto.timezone which specifies a timezone offset in hours. If this property is not set, the offset defaults to UTC (0). Customers should check their devices to ensure that event timestamps from their devices are in UTC and set this new property accordingly.
Added graphs and complex datapoints for status codes that are sometimes included as a negative return value for the Level metric, which should prevent incorrect graphs and false alerts. Added missing descriptions.
Resolved issue that was causing outage updates to be displayed as duplicates of the same event.
Fixed incorrect calculation of In/OutUtilizationPercent datapoint values.
General updates to LogicMonitor’s topology-mapping-specific LogicModules include:
Discontinued matching OUI and LLDP edges on Brocade devices due to non-existent edges being generated.
Added new OIDs for ERT discovery.
Updated all VMware VCSA DataSources to accept credentials via the vcsa.user/vcsa.pass properties. To ensure backwards compatibility, the DataSources will fallback to using esx.user/esx.pass if no VCSA-specific credentials are provided. Customers should migrate their VCSA-specific credentials to the new properties at their earliest convenience.
Added an UptimeDays complex datapoint to represent system uptime in days. Added missing datapoint descriptions.
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.
In This Article