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!
Note: Dynamic thresholds phase two will be activated for all Enterprise customer portals on July 16. At this time, if you currently have dynamic thresholds enabled for any datapoints, the new phase two functionality will automatically be enabled for those datapoints as well. Visit Enabling Dynamic Thresholds for Datapoints for more information on the enhancements and features included in phase two.
Last November, LogicMonitor released phase one of our AIOps Early Warning System. In this first phase, we brought you dynamic thresholds and root cause analysis. As part of our phase two efforts, we’re expanding the capabilities of dynamic thresholds.
In phase one, dynamic thresholds suppressed alert notification routing if the alert’s triggering value was not deemed anomalous by our anomaly detection algorithms. In other words, alert notifications that represented data values that fell within expected data ranges were automatically suppressed for the purpose of reducing alert noise.
With the enhancements available in phase two, dynamic thresholds now also automatically alert on values that fall outside expected data ranges.
By building upon our ability to recognize and proactively act upon anomalous data, we’re giving you the best of both worlds:
See EA Collector – 29.100 for more details.
Upon your account’s upgrade to v.138, import our new and updated LogicModules from the LogicMonitor public repository to expand and enhance your monitoring coverage.
Discovers the Amazon EventBridge serverless event bus and monitors various metrics including invocations, matched events, and triggered and throttled rules.
Monitors auto-failover events, bucket performance, node status, and pool performance for Couchbase Server (formerly known as Membase). For setup and monitoring details, see Couchbase Server Monitoring.
LogicMonitor has released a new monitoring suite for Dell EMC XtremIO that simplifies setup, improves code efficiency, and supports scalability.
Note: This new monitoring suite deprecates 17 legacy XtremIO DataSources. For details on migrating to this new suite, see Dell EMC XtremIO Monitoring.
Discovers and monitors StackDriver data for Cloud Composer, including API requests and latency.
Contains new SysOID map categories. As highlighted in the Updated Monitoring Coverage section, updates are available for Kemp DataSources that take into account these new SysOID map categories.
Provides control group/status and systemd service status monitoring via the systemd-cgtop and systemctl commands respectively. For setup and monitoring details for these new DataSources, see Linux (via SSH) Monitoring.
Deprecates legacy PaloAlto_FW_GlobalCounters DataSource.
Updated the operatingStatusAlerteError complex datapoint name to remove typo (there was an extra lowercase “e” in the name).
Important: Upon updating, LogicMonitor will treat this complex datapoint as a brand new datapoint and all historical data previously collected for it will be lost. You can avoid this data loss by changing the complex datapoint’s name to the new name (operatingStatusAlertError) before importing this updated DataSource. Be sure to exactly match the new name when renaming, including capitalizations.
Updated to additionally assign a value of “NoPing” to the system.categories property for identified Meraki devices.
Added a discovery filter to remove .1 OID results for which Dell returns 0s in order to prevent false alerting.
Added a compatibility check for security acceptance banner messages to the Fortinet_FortiOS ConfigSource
Updated the appliesTo script to ignore devices which do not respond to Ping.
Updated the HP_Product_Info PropertySource to avoid reporting noise on non-HP servers.
Update appliesTo script to work with new SysOID map system category; cleaned up graphs; added various missing datapoint descriptions.
Note: As highlighted in the New Monitoring Coverage section, a new SNMP SysOID Map has been made available for import.
Updated the memory_usage_percent datapoint to account for no limits.
Updated the Technical Notes field with a link to the support article.
Updated the metric type for the Status datapoint; updated grouping method to support grouping by the auto.properties.entityfriendlyname property rather than the GUIDs provided by Azure.
Updated grouping method to support grouping by the auto.properties.entityfriendlyname property rather than the GUIDs provided by Azure.
Added null safe navigation to the Microsoft_SQLServer_Databases DataSource; added code to suppress alerting when a job is disabled to the Microsoft_SQLServer_SystemJobs DataSource.
Removed blank line from Active Discovery script causing script failure; performed minor script cleanup and reformatting.
Updated the idleInterval datapoint’s CDP expression calculation to ignore NetFlow alerts on devices that have either never had NetFlow data or have disabled NetFlow.
Update the Technical Notes field to mention a known bug for EL7-based systems running EL7 net-SNMP 5.7.2.
Added new parsing and null exception handling.
Fixed issue where script was not properly configured for batchscript, which resulted in No Data; fixed alert threshold for the TunnelState datapoint.
Additional exception handling on memEts datapoint.
Improved the script of this built-in appliesTo function for readability, ease of use, and extensibility. These changes will not impact device association.
Updated alert trigger intervals for several datapoints to reduce alert noise.
Moved storage ERI block into Cisco UCS conditional.
Updated the addERI_Cisco_EIGRP PropertySource to allow for multiple Cisco EIGRP ERI.
Miscellaneous updates to the following PropertySources: addERI_Arista, addERI_Cisco, addERI_Device, and addERI_Juniper.
Added multi-threading support to the VMware_vCenter_Topology TopologySource; updated to ensure that ESX hosts managed by the vCenter but not in clusters are captured.
Updated the Cisco_HSRP_L2_HA TopologySource to allow for multiple standby HSRP routers.
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.
In This Article