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!
When viewing alerts triggered by datapoints from the Alerts page, the Overview tab now displays an alert overview graph that plots 60 minutes of data collected for the datapoint. (Previously, this graph was only available on the Overview tab for alerts triggered by dynamic thresholds.)
All alert overview graphs, whether the alert is the result of dynamic or static thresholds, support the following anomaly detection visualization tools:
▲ By default, all alert overview graphs display an expected range (shaded in blue) and plot current data values for the datapoint (represented by a blue line when within the expected range and a red line when outside the expected range). In addition, the one-week offset is optionally enabled for this graph, which plots a signal (in green) that represents datapoint values from exactly one week ago.
This at-a-glance graph and its anomaly visualization tools are useful for quickly understanding the context of the alert, particularly when no predefined graphs exist for the triggering datapoint.
Upon your account’s upgrade to v.140, import our new and updated LogicModules from the LogicMonitor public repository to expand and enhance your monitoring coverage.
The new AWS_Elemental_MediaStore DataSource monitors network, request, and error metrics for AWS Elemental MediaStore containers.
Monitors the AWS Health event log via the AWS Health API.
Monitors Cisco HyperFlex cluster information via Cisco Intersight, as well as monitors security adversities, licensing data, and HyperFlex alarms for Cisco Intersight. We are targeting v.141 for the release of several more Intersight LogicModules, along with setup documentation.
A new DataSource named Cisco_Meraki_Licensing, which monitors license status and days until expiration, has been added to the Cisco Meraki monitoring package.
A new DataSource named Kubernetes_Endpoint has been released that monitors the number of available Endpoints or Endpoint Slices per service, depending on which is available. As discussed in the Updated Monitoring Coverage section, this data was previously monitored by the Kubernetes_Service DataSource.
LogicMonitor has released a new DataSource named Nimble_Array_Info that features an updated data collection method to parse for metrics rather than extracting results from the raw response via datapoints. Exception handling for missing metrics as well as new storage metrics have also been added.
Important: This new DataSource deprecates the Nimble Array Info DataSource. If you are currently using this now-deprecated DataSource, you will not experience any data loss upon importing the new DataSource because of the name variation that exists between the two DataSources. 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 DataSource after you have imported the new one and verified that it is working as expected.
Two new PropertySources (addERI_PureStorage and addERI_AIX) and one TopologySource (PureStorage_Topology) were created for the purpose of supporting topology mapping for Pure Storage nodes and arrays. (As discussed in Updated Monitoring Coverage, several existing LogicModules were also updated for this purpose.)
Updated the following AppliesTo functions with descriptions: isMisc(), isNetwork(), isStorage(), isVirtualization(), and NetScan_discovery_queue.
Updated active discovery script to handle missing or invalid instances. Discovery will no longer fail if a single instance returns “noSuchInstance”.
Updated all datapoints, with the exception of ActiveConnectionCount (Max) and Status (Average), to request Sum metrics.
Updated collection script to account for sensor scale, type, and precision; now ignores all sensors that aren’t measuring temperature. Replaced estimation with code that looks at scale and precision.
Updated the Description field for the addCategory_CiscoHyperFlex PropertySource to indicate the need to manually assign the value of “CiscoHyperFlex” to the system.categories property for devices not configured for SNMP.
Updated to no longer assign the placeholder auto.fooProperty instance-level property.
Added a check for the HTTP return code before parsing responses for the following LogicModules:
The incorrect dead host status set for some Meraki devices (and causing incorrect alert suppression) is now being overridden for the following LogicModules:
For the Cisco_Meraki_Switch_Interfaces DataSource only, the following updates have been made:
For the addCategory_Meraki_API PropertySource only, the “NoPing” category is applied to organizations or networks that have no devices; fixed bug causing the auto.timezone property to be set to null.
Added support for empty files to reduce incidence of false alerts; added checks for error messages that echo output back to eliminate errors in execution from entering the history.
Updated to add properties for resource age, DNS resolution, auth, SSH availability, SNMP status, and WMI availability; added error state properties.
Updated the AppliesTo statement for the HPE_Network_Config ConfigSource to add support for H3C devices.
For the following DataSources, fixed error that was dropping leading 0s from the authentication hash causing active discovery and data collection to fail in the event the hash had a leading 0.
Added Keep-Alive header to request in order to resolve a bug that was causing some incorrectly too-long timeouts to be recorded along with gaps in historical data.
Updated the AppliesTo statement for all DataSources in the Istio Kubernetes monitoring package to additionally return TRUE for pods with label “app = promsd”.
Moved endpoints count from this DataSource to a new DataSource named Kubernetes_Endpoint. Important: Historical data for the numberOfEndpoints datapoint will be lost upon update as this datapoint is no longer present in the Kubernetes_Service DataSource.
This DataSource never collected data; customers can safely delete from their portals.
Updated the PowerShell script to use PSSession.
Fixed an issue in the collection script of the addCategory_Office365Reports PropertySource that was obscuring error messages on failure.
Updated the query used by the active discovery script; updated both collection and active discovery scripts to strip out additional unsupported characters from wildvalues.
Note: Some historical data loss may occur on import of this new DataSource version; however, instances for these DataSources are typically short lived so impact should be minimal.
As part of a datapoint cleanup initiative, missing datapoint descriptions were added to the following DataSources.
Removed the alert threshold from the idleInterval datapoint since the threshold should be dependent on device configuration; updated the Technical Notes field with information about needing to manually set the threshold.
Updated collection script to bypass kernel version checks of net-snmp 5.7.2 or higher if the device’s system.sysinfo property does not contain kernel information and is less than three parts, such as when the property value string only contains the hostname.
As highlighted in the New Monitoring Coverage section, LogicMonitor has released a new Nimble_Array_Info DataSource. This new DataSource deprecates the Nimble Array Info DataSource. If you are currently using this now-deprecated DataSource, you will not experience any data loss upon importing the new DataSource because of the name variation that exists between the two DataSources. 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 DataSource after you have imported the new one and verified that it is working as expected.
Updated the AppliesTo statement of the addCategory_NTPResponds PropertySource to prevent it from applying to devices with a value of “CiscoNTP” in their system.categories property (due to resulting script timeout issues for those devices).
Fixed issue where collection and active discovery scripts were handling null SNMPv3 parameters incorrectly.
Four DataSources (PureStorage_VolumePerformance, PureStorage_VolumeUtilization, VMware_vCenter_HostPerformance, and VMware_vCenter_HostStatus) and five PropertySources (addERI_Device, addERI_ESXi, addERI_HyperV, addERI_Linux, and addERI_Windows) were updated for the purpose of supporting topology mapping for Pure Storage nodes and arrays. (As discussed in New Monitoring Coverage, several new LogicModules were also created for this purpose.)
For the PureStorage_VolumeUtilization DataSource only:
Updated to permit the assignment of a literal * character for the interface.description.alerts_enable property.
Updated collection interval to two minutes; using OperState instead of ifLastChange when iterating over the raw data; added handling for missing uptime values.
Fixed the AppliesTo statement, which was not updated appropriately after being targeted to a specific device for testing purposes.
The following DataSources were replaced and deprecated more than one year ago, but never removed from the LogicMonitor public repository. With v.140, they have been removed from the repository.
Updated active discovery script to check ports before attempting a connection, previously passing a closed port would cause active discovery to fail.
Updated ERIs for the Win_HyperV_VirtualMachines DataSource and addERI_Windows PropertySource to resolve an issue in which virtualized Windows machines were not merging with their parent VMs.
Updated the display name.
In This Article