Updated on December 28, 2021
- Push Metrics enhancement: Percentile aggregation added for sub-minute data submission. Percentile aggregation can now be performed on multiple values to return the value which is greater than the specified percentage.
For example, the 95th percentile is the value which is greater than 95% of the observed values. Percentiles can be used to find outliers for alerts that can be generated within LogicMonitor for values that are outside the norm or above/below a specified threshold.
LogicMonitor v.163 is scheduled to roll out to customer portals from December 27 through January 10.
- JobMonitor now checks the system.ip for devices with different host names and display names. If there is a match, the respective job triggers.
- Fixed an issue that prevented Azure VMs from being removed from LogicMonitor after being terminated in the Azure portal.
- Fixed an issue that caused numberOfAvailableSessionHosts datapoint from displaying the correct data.
- You can now upgrade Autotask URLs to v1.6 using a button in the Autotask Integration settings window in your LogicMonitor portal.
- Improved the user experience on the Logs detail panel. The selected log now moves to the top of the table when the detail panel is opened. Added keyboard keys to scroll through the logs and detail panel.
New and updated LogicModules are available for you to import from the LogicMonitor Public Repository. This section lists the LogicModules that are new in this release, updated in this release, or will be removed in a future release. Changes related to the LogicModule feature will be listed under General Updates.
Provides licensing information per device.
|(8 DataSources, 4 PropertySources, 1 TopologySource)
New coverage for SilverPeak devices using the Orchestrator REST API.
Provides Common Configs required information to support some Sophos Devices.
Updated diff filters to include radius server secret and more.
Added HP devices to conditional for retrieving properties from 22.214.171.124.126.96.36.199.1.1.1 OID.
Removed use of expect and standardized code across suite.
Fixed an issue in disk usage aggregation.
Added Azure cloud host support for private IP address.
Added a new license status “expires soon” for single site-wide license.
|(4 DataSources, 1 PropertySource)
Fixed an issue that prevented properties from being assigned automatically. Added safe navigation to fallback metric source in VMware_VeloCloud_EdgeLinkEventQuality to prevent script failure.
Added support for HTTPS for device properties.
|(1 DataSource, 1 PropertySource)
Updated AppliesTo scripting in PropertySource to persist even after category is set. Added debug print for raw XML response for troubleshooting.
Fixed an issue that assigned incorrect ILPs to LUNs and RAIDs, causing instances to group in storage controllers.
Added debugging error messages when a token cannot be generated.
AppliesTo scripting has been updated to check if a sysoid is found and matches Linux to honor the NoLinuxOpenMetrics flag.
You can add “NoLinuxOpenMetrics” to system.categories to disable any port probing on that device.
Improved decoding of edge states and statuses.
Added check in Active Discovery to ignore null values for null IfIndex.
Used here-strings for WMI credentials for support of special characters.
Removed healthStatus datapoint.
Complex datapoint expression was invalid and datapoint was not intended to be released.
Converted totalRequests datapoint from gauge to counter to provide more meaningful data. Updated description and graph accordingly.
Additional filtering in the script to exclude CloudGenix devices that respond to Isilon OIDs.
Important: This update prevents any newly added CloudGenix devices from having the “Isilon” category applied for the system.categories property. Since categories are not removed by Active Discovery, users must manually update the categories on any affected CloudGenix devices.
Added debug mode and improved code for easier troubleshooting.
Fixed an issue that disrupted grouping for PSUs and data collection for FabricExtender.
Added support for user defined metrics to block and customize threadpool size.
Common Config monitoring DataSource updated for instance creation.
Excluded sandbox portals in AppliesTo.
This table lists LogicModules that we are deprecating in this release. This means that these LogicModules will be removed in a future release. If available, a replacement LogicModule is listed.
|Details||End of Support Date|
|Win_WMI_UACTroubleshooter||Replaced with: Microsoft_Windows_UACTroubleshooter.||12/31/21|
Replaced EMC_VNX2 modules with their corresponding same name modules without VNX2. These modules were duplications that offered extra datapoints which have been added to the standard versions.
Removed duplicate modules.
For the list of LogicModules deprecated over the past five releases, see the support article Deprecated LogicModules.
In this section, you will find announcements about upcoming beta features, updates about ongoing beta features, and information about the end-of-life of existing features.
LogicMonitor APM Lighthouse Program
LogicMonitor APM has been available in a limited release capacity for the past few months. We are now getting ready to expand access with the launch of our Lighthouse Program for users that want access to our APM capabilities. Along with early access, qualified customers and prospects will have the opportunity to influence the early direction of our product and provide feedback to enhance our APM offering.
If you are interested in participating in our Lighthouse Program, please fill out the Google form here.
MGD Collector 30.002 Update
The automatic update to MGD Collector 30.001 was scheduled to deploy on January 10, 2022.
This release, which was scheduled for deployment on October 27, was postponed while we fixed a performance issue.
However, due to the Log4Shell vulnerabilities, the new MGD Collector version will now be 30.002. This version addresses the Log4shell vulnerabilities. This version is scheduled to be automatically installed on January 20, 2022.
No action is required ahead of this date. You may upgrade to MGD Collector 30.002 before January 20 or you may wait for the automatic upgrade to occur. For more information, see MGD Release Update.