LogicModule changes (including New, Updated, and Deprecated LogicModules) are announced for each LogicMonitor release. See Platform Release Notes.
This table tracks the LogicModules that have been deprecated. If a replacement is available, we will provide it before we officially remove the deprecated LogicModules in a future release.
|LogicModule Deprecation||LogicModule Replacement||Details||End of Support Date|
|In the existing version of this module, the wildvalue would get set to the same value for every instance, making all instances duplicates in most cases. Due to this all data was duplicated from a single instance. Wildvalues have been modified to ensure that they are unique. Additionally license types that are subsets of other licenses will now be filtered out if the parent license is not owned. This will ensure that expiration dates that are being reported, are only for licenses types that can expire.|
The datapoint DaysRemaining has been changed to report on expireTime instead of endTime, e.g. reporting on when the license expires instead of the end of the grace period. Grace period days are now no longer directly tracked but DaysRemaining will report negative values during the grace period, with a value of -90 being the standard time frame in which grace period licenses expire. Additionally minor changes to date processing have been implemented so additional date formats for license expirations can be parsed.
Azure Site Recovery Account
|N/A||The Azure Site Recovery Account and Azure Site Recovery EventSources cause alerts on the same events resulting in duplicate alerts. The Azure Site Recovery Account EventSource has been removed to avoid duplicate alerts.||2023-09-15|
|Deprecated addCategory_MySQL and replaced it with the properly labeled addCategory_OracleMySQL. The new addCategory will put the version numbers on the resource if a successful connection can be made.||2023-09-15|
|The deprecated modules have been superseded by new modules that are optimized for vCenter Server Appliance 6.7 through vCenter Server 8.0.x and ESXi 6.5 through 8.0.x. The new modules are named to reflect what they monitor.||2023-09-15|
|AWS_MSK_Cluster is replaced by 2 datasources that support MSK Provisioned and Serverless Clusters separately.||2023-09-01|
|The deprecated modules use JWT, an authentication method that Zoom is planning to turn off on on September 1, 2023. For more information, see Zoom Developer Documentation.|
Zoom monitoring remains available via the LogicMonitor SaaS integration.
|Oracle_Database_TableSpaceUsage||Oracle_Database_TableSpaceUsageMaxGrowth||These modules report the same data, however Oracle_Database_TableSpaceUsageMaxGrowth has two additional datapoints.||2023-09-01|
|N/A||Microsoft is deprecating global and cluster-named init scripts for Databricks, which LogicMonitor currently uses for Databricks monitoring. These scripts will be disabled on September 1, 2023 by Microsoft, at which point LogicMonitor’s existing Databricks integration will cease to work.|
Based on the current integration utilization, we will not be replacing the integration in September. Submit your feedback if an out of the box Databricks monitoring is something you need.
|Microsoft_Azure_APIManagement||Microsoft_Azure_APIManagementV2||The Microsoft_Azure_APIManagement DS contains metrics that will stop working in August 2023. For more information, see Microsoft Azure Metrics Retirement (Aug 2023)||2023-08-31|
|Config_Cisco||Config_Cisco_Generic||Combined functionality into single module.||2023-07-14|
|Kubernetes_Scheduler||Kubernetes_Schedulers||Changed module from single instance to multi-instance allowing you to monitor multiple instances of the Kubernetes Schedulers (in case you use your implemented Schedulers).||2023-06-15|
|LogicMonitor_Collector_ScriptCache||LogicMonitor_Collector_ScriptCache_JMX||Added new JMX Metrics for monitoring script cache more efficiently.||2023-06-15|
|AWS_SageMaker||AWS_SageMaker_Endpoint||The replacement module supports more versions of the technology connected with SageMaker AWS service and removes datapoints that were not working.||N/A|
|Dell_PowerConnect_Interfaces||SNMP_Network_Interfaces||Dell_PowerConnect_Interfaces was initially developed to address discovery-based indexing issues that were seen in PowerConnect environments that presented collection issues where duplicate interface descriptions existed. These issues have since been addressed in SNMP_Network_Interfaces which also includes stability fixes in larger environments.||2023-04-23|
|HP_Product_Info||Device_BasicInfo||Consolidated functionality into fewer PropertySources to improve portal functionality and reduce collector load.||2023-03-31|
|SNMP_Interfaces_Mode||Device_BasicInfo||Consolidated functionality into fewer PropertySources to improve portal functionality and reduce collector load.||2023-03-31|
|AWS_EC2_ScheduledEvents||AWS Health Events||Replaced the AWS_EC2_ScheduledEvents datasource with the AWS Health Events eventsource to reduce data duplication and CloudWatch costs.||2023-03-21|
|AWS_Elasticsearch_DataNodes||AWS_OpenSearch_DataNodes||Renamed the datasource and updated metric paths to follow AWS changes, and updated datapoints and graphs.||2023-02-21|
|AWS_Elasticsearch_CPUCreditBalance||AWS_OpenSearch_CPUCreditBalance||Renamed the datasource and updated the datapoint description.||2023-02-16|
|AWS_Elasticsearch_MasterNodes||AWS_OpenSearch_MasterNodes||Replaced mentions of Elasticsearch with OpenSearch and fixed linting issues.|
Note: Historical data will be lost after migrating to this new module.
|AWS_Elasticsearch_MasterNode||AWS_OpenSearch_MasterNode||Added MasterReachableFromNode datapoint.||2023-02-02|
|Details||End of Support Date|
|LogicMonitor deprecated the recently released PaloAlto SD-WAN package. |
Recommendation: Use LogicMonitor’s native SNMP capabilities to monitor Palo Alto Network Prisma SD-WAN Instant-On (“ION”) devices (formerly Cloudgenix).
|LogicMonitor has rewritten the Oracle modules to be consistent with the other database modules. The functionality of these modules were moved into existing modules.||2022-11-30|
|Replaces legacy DataSource.||2022-09-15|
|Powershell-based modules were replaced by the Office365 SaaS integration last year.||2022-31-08|
|This module only applies to collector versions that are no longer supported (24.106 through 29.105). Current minimum collector version is 30.002.||2022-15-08|
|Removed redundant ERI property sources with functionality that is already supported in other ERI sources.||N/A|
|Created a new Cisco memory module that merges existing Cisco memory modules. Added support for monitoring cisco-enhanced-mempool MIB.||2022-07-08|
|This module was creating instances to store system properties. The data provided by these instances is now available through addCategory_EMC_VNX.||2022-07-08|
|This DataSource experiences monitoring data gaps and API timeouts that affect the functionality of other Cisco Meraki DataSources and should be deleted or disabled. Switch connection status and client count remain available via the Cisco_Meraki_Switches Datasource.||2022-08-05|
|Replaced the old module that did not filter services properly and reported intermittent or no data for a number of datapoints.||2022-06-17|
|Updated WMI class from Win32_PerfRawData_NTDS_NTDS to Win32_PerfRawData_DirectoryServices_DirectoryServices.||2022-05-16|
|Updated to current conventions and now uses the Win32_PerfFormattedData_Counters_ProcessorInformation WMI class.||2022-04-22|
|Branched out into four separate modules to better serve specific aspects of vCenter. Note: VMware_vCenter_Topology should be deleted or set to “false” to prevent interference with new modules.||2022-03-15|
|This module created confusion and excessive alerts. The info provided is now stored as a property applied by Microsoft_Powershell_Info.||2022-03-09|
|Added new module Microsoft_IIS_Server identical to WinIIS- but with a more narrow AppliesTo in order to prevent excessive Collector runs on devices that will never work.||2022-03-09|
|Did not provide meaningful actionable data.||2021-04-12|
|Merged authentication connection checks into Microsoft_SQLServer_Connections so all connection verification is in one module.||2021-02-11|
|VMware_vCenter_Topology will remain in the core with the ApplesTo set to “false” until 2/11/22 to ensure conflicts do not occur when importing the replacements.||2021-02-11|
|Previous versions no longer work due to a hard JAR dependency. The new modules expand on the metrics provided by the old modules.||2021-01-20|
|Details||End of Support Date|
Module is no longer supported. For monitoring Windows services
Windows_TimeOffset used a collection method that guaranteed a delayed result due to time difference calculation occurring server-side rather than at collection.
The replacement is now scripted with attempts to improve accuracy and better communicate the variation in timing due to time spent on our WMI query.
|(3 DataSources) |
These modules created excessive instance counts with all runs of a backup, including those that were expired, as separate instances. Data provided was not actionable and created unnecessary collector load.
The replacement modules provide the same data for the latest backups.
|(4 DataSources) |
Combined existing uptime modules into a single new module to remove duplicate coverage and streamline support.
|Deprecated due to duplicate monitoring and altering.||2021-12-10|
|(3 DataSources) Gathering billing data via file is now deprecated.|
You should use the BigQuery modules for GCP billing and remove the GCP storage buckets used for storing billing files.
|(1 DataSources) Deprecated module was querying OID that returns invalid data. New module tracks queries, responses, and referrals per zone.||2021-11-10|
Created excessive instances.
Overlap between Cisco_Nexus and Cisco DataSources. Deprecated duplicate modules to prevent double monitoring or alerting.
Metrics for Cisco_Nexus_CPU_Memory are present in the latest version of Cisco_CPU_Usage. Metrics for Cisco_Nexus_Fan and Cisco_Nexus_FRU_Status are present in Cisco_FRU_Power.
|Deprecated: Cisco_Product_Info |
|(1 PropertySource) Deprecated in favor of Device_BasicInfo.||2021-10-15|
|(1 DataSource) Use composite of local and remote tunnel addresses instead of tunnel index to prevent duplicate instances. Deduplicate tunnel data returned under different tunnel indices. Customers wishing to preserve historical data should disable the deprecated module to prevent duplicate collection.||2021-08-04|
|(2 DataSources) No longer in use for Topology generation.||2021-08-27|
|(DataSource) Provides the same data as the CPU Cores- DataSource.||2021-08-27|
|(2 DataSources) Unable to report consistent data across devices/instances.||2021-08-27|
|(DataSource) Did not provide useful data. It is recommended that JobMonitors be used to monitor crontab entries.||2021-08-27|
|(DataSource) Change active discovery and collection to batchscript. Try and handle renamed or missing instances.||2021-07-02|
|(DataSource) New module uses scripted active discovery to ensure that instance names are unique and nonephemeral.||2021-05-21|
|Modules generate an excessive amount of instances for ephemeral devices, in some cases multiple for a single device. These modules are known to cause performance issues and should be deleted or disabled.||2021-07-01|
|Old module did not produce unique wildvalues, new module uses scripted discovery to produce unique wildvalues by combining test name and owner. It is recommended that the old module be disabled to preserve historical data.||2021-04-22|
|Deprecate modules in favor of single a DataSource for all backup jobs. New DataSource uses pagination which provides significant performance improvements, particularly for large deployments.||2021-04-07|
|Customers wishing to preserve historical data should disable these modules to prevent double collection and alerting. Please update SNMP_Filesystem_Status and SNMP_Filesystem_Usage to at least v1.1 before disabling these modules as alerts were not set in earlier versions.||2021-04-07|
|(2 DataSources) All the functionality of these now-deprecated DataSources is present in the SNMP_Network_Interfaces DataSource, along with significant enhancements including additional datapoints, scripted data collection for improved performance, instance-level properties that provide for additional filtering capabilities, and more precise alerting to eliminate alert storms caused by the old DataSources.||2021-03-19|
|(2 DataSources) Postfix no longer provides the data requested by the modules.||2021-05-24|
|(DataSource) This DataSource was creating excessive instances, resulting in degraded Collector performance.||2021-05-05|
|(2 DataSources) Released in v.145, Cisco_CPU_Usage performs the same functions as these deprecated DataSources in a more efficient manner.||2021-03-08|
|(4 DataSources) The replacement DataSources use scripted Active Discovery to ensure unique instance naming, a known issue with the now-deprecated DataSources.||2021-03-08|
|(DataSource) Development DataSource that was inadvertently published.||Immediate|
|(DataSource) The now-legacy DataSource produced indecipherable instance names. The replacement DataSource remedies this as well as features new overview graphs and datapoint descriptions..||2021-03-08|
Unomaly Anomalies Frequency Spikes
Unomaly Known Events
Unomaly New Anomalies
New LM Logs feature, released in fourth quarter of 2020.
|(3 EventSources) Functionality has been fully replaced by LogicMonitor’s new LM Logs feature.||2021-02-17|
|(1 DataSource) It has been determined that all data gathered by this DataSource is being reported more robustly through the existing NetSNMPCPUwithCores and NetSNMP_Memory_Usage DataSources, making it redundant and unnecessary.||2021-02-09|
|(1 deprecated DataSource) Enhancements featured by replacement include an updated AppliesTo statement that includes OpenBSD systems; updated filters to exclude /proc and /dev and allow discovery of files between 0-100 bytes on filesystems; new complex datapoints; and support for drives over 8 TB and block sizes other than 4 K.||2021-01-19|
|(7 deprecated DataSources) The replacement DataSources apply to the cluster VNN rather than each node individually, significantly reducing the incidence of duplicate alerts. |
Note: The six replacement DataSources listed here are part of a bigger monitoring package for Microsoft Windows Failover Clusters that was released in v.146.
|(1 DataSource) Converted to a scripted DataSource and uses an additional OID to resolve duplicate wildvalues.||2021-01-04|
Liebert Power lines
Liebert Temperature probes-
Liebert UPS Temperature probes-
|(3 DataSources) Rewrote DataSources as scripted SNMP; merged monitoring of temperature and UPS temperature probes into a single DataSource; added new power and voltage metrics for power lines monitoring; fixed an incorrect filter for power lines.||2021-01-04|
|(1 DataSource) LogicMonitor released five new DataSources that provide 15 additional datapoints and group related metrics into separate DataSources, making it easier to hone in on specific aspects of your portal. For more information, see LogicMonitor Portal Monitoring.||2021-01-04|
Importing LogicModule replacements
When importing a replacement LogicModule, you will not experience any immediate data loss due to the name variation that LogicMonitor expressly adds. However, there will be a diversion in data collection between the deprecated and new LogicModule, and 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 monitoring of the DataSource instances at the resource or resource group level after you have imported its replacement. When DataSource monitoring is disabled in this way, it stops querying the host and generating alerts, but maintains all historical data.
At some point in time, you may want to delete the legacy DataSource altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSource monitoring, see Disabling Monitoring for a DataSource or Instance.