LogicMonitor v.188 is scheduled to roll out to customer portals from June 12, 2023 through June 21, 2023.
Updated on July 10, 2023
- Topology: After you create a mapping, you can edit the mapping by adding, modifying, or deleting the manually created connections. For more information, see Editing Manually Created Connections.
- Feature Highlights: General Availability of the MongoDB Atlas integration. Open Beta for LogSource Module. Multiple Collector releases. PDF for Topology Maps.
- General Updates: Netflow mass delete port, ASN, and DNS mappings. REST API V3 officially supports bearer token. New and updated LogicModules available in your LogicMonitor public repository.
- Updated Monitoring: New modules to monitor MongoDB Atlas and topology support for Helm Chart releases.
Important: If you are using unsupported browsers (for example, Internet Explorer) after 28 June 2023, you must switch to a browser that LogicMonitor supports to maintain access to features in your portal, such as Reports. For more information, see Supported Browsers in the Product Documentation.
For more information regarding this requirement, see the TLS 1.2 to become the minimum TLS protocol level for all AWS API endpoints documentation from AWS.
General Availability of MongoDB Atlas Integration
The MongoDB Atlas Integration is now generally available. This integration enables you to monitor Atlas managed databases with LogicMonitor’s cloud (API-based) integration. MongoDB Atlas database resources discovered are billed as cloud resources. For more information, see MongoDB Atlas Project Integration in Product Documentation.
New module for enabling and configuring the sending of log data to LM Logs. LogSource contains details about what logs to get and where to get them, and which fields should be considered for parsing. LogSource is available for Syslog, Windows Events, Kubernetes Events, and other common log data sources. LogSource is moving to an open beta and will be available for all LM Logs customers to use. For more information see LogSource Overview in the Product Documentation.
Multiple Collector Release
To support various enhancements and bug fixes, the following Collector versions were released in May and June.
|EA Collector 34.100
Note: This version features an Open Beta for non-privileged WinRM Windows Collector.
|1 June 2023
|EA Collector 33.401
|23 May 2023
|GD Collector 34.000
|17 May 2023
|GD Collector 33.004
|2 May 2023
Topology Mapping PDF
You can now export a Topology Map to PDF format. For more information, see Exporting Map.
- Added “Http(s) Load Balancer – Regional” to the service level in the GCP settings to avoid confusion with region filtering.
- You can now view the usage relative to the committed number for cloud resources in the Account Information.
- Fixed an issue that caused EC2 monitoring to poll regions that were not selected for monitoring.
- Duplicate Log records are inadvertently returned when queried for different relative time ranges.
- You can now run an ad-hoc report without being blocked by security policies in different browsers, regardless if you have reporting authentication enabled.
Comparing Multiple Services Data
- You can now select services from the Topology widget and view impact analysis of services on the overall application under RED metrics widgets. This allows you to see the impact of an individual or multiple services on the application. For more information, see “Comparing Multiple Services Data” section in the Traces Page Overview Product Documentation.
- Fixed an issue that prevented MS Teams QoS data from being reliably collected and displayed.
- You can now mass delete port, ASN, and DNS mappings. This can be accomplished using multiple model IDs and performing the mass delete of the IDs. Prior to this enhancement, you could only perform a delete of a single mapping at a time. For more information, see Deleting Mappings in Bulk in the Product Documentation.
- You can now edit and remove nodes in your Topology maps.
- The bearer token is now officially supported in the LogicMonitor REST API V3. As a result, you can now access the Bearer Token information in Settings (Settings > Users & Roles > API Tokens tab > Bearer tab) regardless of your LogicMonitor licensing.
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.
|New monitoring for MongoDB Atlas
|PropertySource to assist in identifying and excluding Panorama devices from modules that are not applicable.
|Datasource for MediaTailor
|DataSource for GCP Managed Services for Microsoft AD
|Topology for Helm Chart releases
|Updated the default alert message to reflect accurate error information
|Added event source to log metadata
|Changed encoding handling for ‘&’ under alias and description properties, and added 1 Tbps max values to in/out Mbps to prevent spikes due to counter wraps.
|Blocked HSRP MACs from being set as L2 ERI in addERI_Cisco
|Fixed handling of large values, and added checking for values to prevent division by zero.
|Updated the Automatically Delete Instance setting for three datasources to fix the active discovery of unmonitored region instances.
.toInteger() to cisco.ipsec.aggtun.timeout and cisco.ipsec.aggtun.threadpoolsize props import.
Incremented the allowed max for cisco.ipsec.aggtun.timeout to 180 seconds from 45 seconds.
|Used new PropertySource that identifies Panorama devices to update PaloAlto_FW DataSources to exclude Panorama devices.
|Removed interface edge setting for CDP/LLDP entries with unclaimed ports.
Match CDP/LLDP interfaces to IFMIB interfaces also on interface name.
|Updated to inform of migration to KSM modules.
|Updated latest datapoints to fix the NullPointerException.
|Added debug mode to collection script to improve certificate troubleshooting experience.
|Fixed an error in ordering for removal of ports to exclude in port scan with
exclude.ports host property.
|Updated code to check cookie expiration using additional date formats.
|Added null filtering for instances.
|Added \n support to custom responses in common configs.
|Alerts have been removed from this module as a result of the module’s design to assist with initial configuration. All errors are displayed as instances and found by Active Discovery every 15 minutes. The new module for monitoring SQL databases is Microsoft_SQLServer_ConnectionStatus and runs every minute to alert of failure. This module was updated up to use snippets and to create a WMI instance only when WMI is not enabled.
|Expanded list of devices to use SNMP
getconcurrent method to include Cisco devices that are not responding to rapid throughput ramps.
|Added optional host property
ssl.cert.monitor to allow users to exclude devices from SSL certificate monitoring by setting the value to false. For more information, see SSL Certificate Monitoring in the Product Documentation.
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. For the history of deprecated modules, see Deprecated LogicModules.
|End of Support Date
|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).
|Added new JMX Metrics for monitoring script cache more efficiently.
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.
Deprecation of Microsoft Azure Databricks Monitoring
LogicMonitor is deprecating monitoring for Microsoft Azure Databricks and this functionality will be removed in a future release. For more information regarding the deprecation, see the Cluster-named and cluster-scoped init script migration notebook documentation from Databricks.
Recommendation: If an out-of-the-box Databricks monitoring solution fits your environment, submit feedback directly in your LogicMonitor portal using the Support Resources. For more information, see Accessing Support Resources in the Product Documentation.
AWS Organizational Units
Added support for AWS Organizational Units to accelerate the configuration of AWS Accounts. This feature is currently in Beta. To become a Beta participant, contact Customer Success.