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!
v.142 Highlights:
!(InstanceNameA | InstanceNameB)
"source":"##HOST####WEBSITE##"
"source":"##HOST## ##WEBSITE## ##AGENTID## ##AGENT_DESCRIPTION##"
Recently released to the LogicMonitor public repository, import our new and updated LogicModules to expand and enhance your monitoring coverage.
Three new DataSources have been released to replace the now-deprecated and more general Arista_Switch_Storage DataSource. The new DataSources (Arista_Switch_FlashStorage, Arista_Switch_Memory, and Arista_Switch_StorageUsage) filter out instances to allow for separate DataSource monitoring of memory, flash storage, and standard storage. Alerts have been added for Arista_Switch_StorageUsage.
For improved FortiGate topology mapping operations, two new TopologySources (Fortinet_FortiGate_HA and Fortinet_FortiGate_SDWAN) for generating HA and SDWAN edges respectively have been created. In addition, one new PropertySource (addERI_Fortinet_FortiGate) to support ERI discovery for Layer 2, Layer 3, high availability and SDWAN ERIs has been added.
Note: As discussed in the Updated LogicModules section, updates to two existing LogicModules are also available for improved FortiGate topology mapping.
A new PropertySource named addCategory_NimbleSSH was added to the HPE Nimble monitoring suite. This PropertySource tests SSH access to Nimble devices and applies the “NimbleStorageSSH” category.
As noted in the Updated LogicModules section, enhancements have additionally been made to several existing HPE Nimble LogicModules.
Collects metrics for NSX manager system resource utilization and component status; NSX controller resource utilization; uptime and node failover status; and edge service health and interface throughput. Monitors configs for NSX controllers and edge services. For setup and monitoring details, see VMware NSX Monitoring.
Fixed unclear descriptions and alert messages on the humidity threshold breach datapoints.
Added missing metric names that were causing data collection to fail.
Removed three complex datapoints (operatingStatusAlert*) and moved their alerting to the OperatingStatus datapoint.
Important: Any instance-level tuning or alert rule configurations currently referencing these three removed complex datapoints will need to be reconfigured to reference the OperatingStatus datapoint. Historical data for the OperatingStatus datapoint will not be impacted, but historical data will be lost for the three removed operatingStatusAlert* complex datapoints.
Removed log4j usage due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher; updated filters for the DifferenceTest config check.
Removed log4j usage due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher.
Removed unused jackson-databind import to align with Collector versions 29.102 and higher.
For improved topology mapping operations, updated the addERI_Linux PropertySource to set “Switch” as external resource type for Dell EMC networking devices.
Updated to use the actual hostname instead of its string representation to generate values for the auto.network.names property. This prevents invalid values from being set for the property due to DNS resolution issues.
For improved FortiGate topology mapping operations, updates have been made to the Fortinet_FortiGate_HighAvailabilityPeers DataSource and the addERI_Device PropertySource.
Note: As discussed in the New LogicModules section, three new LogicModules have been released for improved FortiGate topology mapping.
Updated the AppliesTo statement to use new “NimbleStorageSSH” category set by the newly-released addCategory_NimbleSSH PropertySource for the following SSH-based LogicModules: Nimble_Array_Info, Nimble_HDD_Disks, Nimble_SSD_Disks, Nimble_Volume_Latency, and Nimble_Array_Properties (PropertySource).
Updated the regex in the Linux_SSH_Filesystems DataSource to handle output split on multiple lines; added debug mode.
Updated the Linux_SSH_Info PropertySource to use the actual hostname instead of its string representation to generate values for the auto.network.names property. This prevents invalid values from being set for the property due to DNS resolution issues.
Removed usages of the commons-codec library, to align with Collector versions 29.102 and higher.
Due to changes to the Azure Service Insights API, the collection interval for this DataSource has been increased to one hour. The previous one-minute interval was resulting in data collection issues caused by too-frequent polls of the API.
Increased the data collection interval to five minutes to match Azure’s recently adjusted minimum allowed collection frequency. The previous one-minute interval was resulting in gaps in historical data.
Updated to support Microsoft Office 365 licensing SKU updates (see Microsoft documentation for a current listing of SKUs); added datapoints and graphs to track the total units.
Important: There may be some historical data loss upon import due to instances being deleted and replaced with instances corresponding to the updated SKUs.
Changed the metric type of the neighborEvents datapoint from gauge to derive; added datapoint and graph for the retransmit queue length.
Fixed misleading description and alert message for the swap_pct_used datapoint found in the PaloAlto_FW_SystemResources DataSource.
Removed log4j usage from the PaloAlto_FW_CLIConfigs due to incompatibilities with the version of the library bundled with Collector versions 29.102 and higher.
Updated wildvalue to exclude special characters in instance names.
Important: This may result in historical data loss for existing instances with special characters in their names due to new instances being created with sanitized names.
Added StatusAlert complex datapoint similar to the datapoint already present in the snmp64_If- DataSource. Alerting has not been moved to the new datapoint to prevent instance-level alert rule changes. Note: An improved interfaces DataSource is targeted for release in an upcoming version.
General updates to LogicMonitor’s topology-mapping-specific LogicModules include:
Added new SystemStatusMemTotal_KB datapoint for total system memory; updated memoryUtilization complex datapoint to account for total memory, buffers and cache.
Change: Added safe navigation to the VMware_vCenter_Topology TopologySource to resolve topology generation issues resulting from an unknown HA state.
Updated the Capacity Detail graph to scale by bytes rather than gigabytes.
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.
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 October 6 (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
