v.178 Release NotesLast updated on 14 March, 2023
LogicMonitor v.178 is scheduled to roll out to customer portals from November 21 through November 30.
- Feature Highlights: Added compatibility for ServiceNow Tokyo Platform to LM Integrations in the ServiceNow Store. Released a new version of the LogicMonitor Terraform integration. Released a new monitoring package for Juniper Mist. Released a new Modules page to replace LM Exchange.
- General Updates: Added service-based metrics to the details panel on the Traces page. Improved the user experience for querying in the Logs page. Added the capability to configure the Collector entirely via Helm chart for Container Monitoring.
- Updated Monitoring: New modules for monitoring AWS MQ, Argus components, Azure Recover Service RTO, and Windows Events in LM Logs.
New Modules Page
Modules is a new user experience that provides access to My Module Toolbox and Exchange. My Module Toolbox is a comprehensive view of your modules, where you can manage and update your installed modules. Exchange is where you go to install new modules from LogicMonitor or from the LogicMonitor community. Modules replaces LM Exchange, however, you can still access Legacy Exchange. Future enhancements will include a new module editor, where you can create new modules or edit existing ones.
For more information, see the following articles in the product documentation:
New Monitoring for Juniper Mist
New monitoring package for Juniper Mist with streamlined device onboarding using Enhanced Script Netscan. For more information, see Juniper Mist Monitoring in the product documentation.
Compatibility with ServiceNow Tokyo Platform
LogicMonitor is now compatible with the ServiceNow Tokyo Platform for the following integrations available in the ServiceNow Store:
- LogicMonitor CMDB Integration
- Service Graph Connector for LogicMonitor
- LogicMonitor Incident Management Integration
LogicMonitor Terraform Integration 2.0.3
You can now find the latest version of LogicMonitor integration for Terraform on the Hashicorp Terraform Registry. This version includes a beta feature called bulk_resource that allows you to add resources over 500 resources at a time. This feature is disabled by default.
Warning: This bulk_resource feature is in beta and may cause performance degradation.
For more information, see LogicMonitor on Hashicorp Terraform Registry.
Application Performance Monitoring
- You can now use the Metrics tab within a Trace timeline page to view critical RED metrics corresponding to their Service. For more information, see Traces Page Overview.
- The option to delete cloud accounts in the LM Cloud page is now consistent with the placement for the delete options in other areas of the LogicMonitor portal.
- Fixed an issue where certain Azure cloud devices were not triggering an alert when they should.
- Re-configured out-of-bounds alert thresholds for AWS RDS to alert when the available burst credits approaches the lower threshold.
- Adjusted AWS CodeBuild API calls to eliminate an error that would show when there were no projects.
- You can now configure the Collector entirely through the Helm chart instead of editing the
agent.conffile located on the Collector.
- Removed the Preserve dialog that erroneously displayed in some portals when updating LogicModules. A modern version of this is coming soon with the LM Exchange revamp.
- You can now view nested metadata values in the Fields panel and add the metadata as columns in the Logs table.
- You can now sort columns in the Logs Aggregate tab in ascending and descending order by clicking the column header. You no longer need to define the sorting in the query.
- Reconfigured the default size of the logs query bar to reduce the amount of white space on the LM Logs page. The query bar will expand with a new line (shift+Enter), or overflow text.
- Log count in the Log Field pane for resource is mismatched.
- Log aggregate queries for 100K and more logs returns a time out error.
- You will now only see the View Permission column display in the User Access > Users list if you selected the column under User Access Table Settings > Manage Columns.
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 AWS MQ queues and topics, per broker.|
|New monitoring for Argus components.|
|New monitoring package for Juniper Mist with streamlined device onboarding using Enhanced Script Netscan.|
For more information, see Juniper Mist Monitoring in the product documentation.
|New module for monitoring for Azure recovery service RTO.|
|New module for monitoring Windows events in LM Logs.|
Nimble Volume Usage
|Increased performance by reducing calls to access hostProps and passing null instead, since hostProps is already known to SNMP functions.|
|Changed instances to delete data after 30 days instead of immediately.|
|Removed unused Apache Commons imports that included classes identified as having a security vulnerability (https://nvd.nist.gov/vuln/detail/CVE-2022-42889).|
|Added print statements in collection to account for potential alternative wildvalues assigned in active discovery.|
|Module updated to use our new SNMP snippet (featuring more robust retry logic and stricter maximum timeouts).|
Fixed an issue where non operational sensor metrics would be used instead of operational versions of the same sensor.
|Added another casing option to lookup table for drive state.|
|Expanded API call function to include 500 server errors with 404 not found errors in accepted failures so that individual failed API calls do not prevent other API calls from running.|
|Fixed logic to evaluate string for “inactive” prior to “active”.|
|Add new state to Azure Replication Job “state” datapoint to indicate “CompletedWithInformation”.|
|Fixed complex datapoint to capture all error statuses.|
|Updated select statement and module display name.|
|Sanitized responses to remove “&” and “and” which do not parse correctly and prevent proper data collection.|
|Fixed typo in display name.|
|The following improvements have been made:|
* Better handling for interface type ILP, expanded Juniper devices using getConcurrent SNMP method
* Fixed uptime units for determining alerting on status flaps
* Improved functionality in custom alert_enable host property
Expanded options for alert_enable host properties that allow you to use regex match patterns to identify instances to alert on for status and flap. Previously, the custom property “interface.description.alert_enable” was linked to the instance level property “auto.interface.alias” which reflects the raw alias value configured on the device. To expand capabilities and correct the naming mismatch, the functioning of this property was adjusted and two additional properties for filtering were added.
The new custom properties and the ILPs they compare against are the following:
* interface.description.alert_enable : system.instanceDescription
* interface.alias.alert_enable : auto.interface.alias
* interface.wildalias.alert_enable : auto.interface.wildalias
Note: auto.interface.alias closely matches the alias assigned at a system level which is sometimes left blank. auto.interface.wildalias will match the instance display name in LogicMonitor.
For more information, see Interface Status Alerting in the product documentation.
|Added an optional unc.subrtactFolderCount instance property with a value of 2 if your total is counting “.” (current directory) and “..” (parent directory) in your OS’s dir /a /s total output.|
|Added VBR connection and disconnect to facilitate monitoring with a local collector.|
|Fixed ERI and ERT for VMware ESXi and vCenter devices.|
|Fixed SystemUptime datapoint description to use microseconds instead of seconds for the unit.|
|Added safe navigation to prevent possible execution errors.|
|Updated to allow for customization of port used in connection via host property unifi.port.|
|Updated to differentiate between client servers and connection servers.|
|Fixed issues with ERI endpoints.|
|Improvements to device connections.|
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.
|LogicModule Name||Details||End of Support Date|
|Identified that both wildvalue and wildalias were not always unique and updated both fields to be unique using interface ID and name, respectively. Because this change resets historical data, the previous version has been deprecated and replaced with the new datasource.||11/11/2022|
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.
Jira Service Management Integration
You can now integrate LogicMonitor with Atlassian’s Jira Service Management to automate your incident management workflows in Jira based on LogicMonitor alerts. This feature is currently in Beta. To become a Beta participant, contact Customer Success.