LogicMonitor v.180 is scheduled to roll out to customer portals from January 2 through January 11.
- Feature Highlights: General availability of Application Topology. Updated the OpenTelemetry Collector. Alert message customization for Slack integration. New topology and config monitoring for Kubernetes.
- General Updates: Improvements to Microsoft Azure monitoring. Enhancements to Collector resources. Expanded support for custom HTTP integrations.
- Updated Monitoring: New modules to monitor Juniper Mist, Aruba ClearPass, Kubernetes configurations, and more.
Application Topology General Availability
Application Topology provides you with a real-time view into your application’s service architecture. You can automatically see relationships between services based on the ingested traces. The ability to view critical RED metrics such as throughput (requests per minute), error rate, and latency (average duration) makes it possible for you to quickly identify where bottlenecks and dependencies are within their application. For more information, see the following:
New OpenTelemetry Collector version 2.0.10
The OpenTelemetry Collector has been updated to version 2.0.10 for application performance monitoring. This release includes the following updates:
- You can now seamlessly export logs, and traces to the platform with a simplified lmexporter leveraging the LM Data SDK. For more information, see LogicMonitor Go Data SDK from LogicMonitor.
- The retry interval of the collector credentials has been reduced from 45 minutes to 15 minutes.
- LogicMonitor now uses OpenTelemetry Collector Contrib version 0.50.0. For more information, see OpenTelemetry Collector Contrib version 0.50.0.
- LogicMonitor now uses Fluent bit version v1.9.0. For more information, see Fluent bit version v1.9.0.
- The overall installation process has been improved, especially the retry mechanism.
Alert Message Customization for Slack Integration
You can now customize the alert body that is sent to the Slack Channel. You can customize this messaging in your LogicMonitor portal.
New Kubernetes Monitoring
You can now use topology and config monitoring for Kubernetes cluster roles, cluster role bindings, and service accounts. This allows you to have more visibility into your cluster RBAC, specifically changes to RBAC.
- You can now track “Monthly Datapoints Collection Per Device” soft limits on your Accounts page. These features will be released in stages, and may not be available in your account with this release.
Application Performance Monitoring
- You can now sort traces and spans on the Traces page by duration with a window up to 6 hours.
- You can now query up to 45 days of Spans with a max time window of one day. Previously, the retention period was 14 days.
- Updated Microsoft Azure monitoring for VM availability and memory usage. For more information, see Updated LogicModules.
- Updated the PostgreSQLFlexible datasource to show BackupStorageUsed metric with the correct update time of five minutes.
- For Collector resources, the “Failover Exclusion” option in the Manage Collector settings is now disabled by default.
- For Collector resources, the “Preferred Collector” selection is now disabled because Collectors are configured to monitor themselves. Previously, you could set a Collector to be monitored by a another Collector, which would report the preferred collector metrics as its own.
- When creating datasources, you can now use decimal numbers in the alert threshold expression field and choose field preservation for a wild value field.
- Expanded support for custom HTTP Integrations to now accept Accept null and valid charsets with valid MIME type in header content-type for integrations.
- Added log alerting support for logs not correlated to a LogicMonitor-monitored resource. For deviceless log alerts, the log pipeline is automatically created as a resource to associate all deviceless log alerts with.
- Fixed an issue for log resource mapping configuration using the system.ips property. Previously the IP address in the log would only attempt to match the first IP listed in resource’s system.ips value if multiple IPs were present. Now all values in the system.ips property are considered when attempting to map logs to LM resources.
- Added advanced filtering support to v3 API which allows you to refine the API results. The advanced filters are applied to key-value pairs where values are in JSON format. For more information, see REST API Advanced Filters.
- Added object quota limits for metrics collection. On the Accounts Information page, the Monthly Datapoints Collection Per Device will indicate the number of metrics (data) collected since the start of the month. For more information, see Object Quota Limit for Metrics Collection.
Note: This feature will be rolled out in phases, so not every customer will see it in LogicMonitor v180 release.
- You can now delete saved maps in the Topology Maps table, if you have the appropriate roles and permissions for this action.
- Interface mapping labels previously displayed the datasource name before the interface label, making it difficult to read the interface name.
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 Aruba ClearPass using SNMP for data collection.|
|New monitoring for AWS MQ.|
|New modules to help with topology troubleshooting and property interface details pane view in the case where SNMP_Network_Interfaces is not applied.|
For related modules updates, see Updated LogicModules.
|New topology mapping for ISIS and Cisco ISIS neighbors.|
For related modules updates, see Updated LogicModules.
|New modules dedicated to device health metrics consistent with similar modules in package.|
For related module updates, see Updated LogicModules.
|New module to monitor health (Packet Loss (%), Jitter (ms), latency (ms)) for SD-WAN overlay tunnels|
For related module updates, see Updated LogicModules.
|New topology mapping (including Storage Classes, Pod Disruption Budget, and Network Policies) and configuration monitoring for Kubernetes.|
|Changed active discovery and collection methods to script and batchscript to add handling for discrepancies discovered in some APC devices between values returned for SNMP get vs walk calls.|
|Made exclusion of aurora devices on AWS_RDS more broad. Note: this change will cause any devices containing “aurora” in system.aws.engine to no longer have this module applied.|
|Added a note in module Technical Notes in order to address the variance in the data output between SNMP vs Cisco CLI.|
|Added formatting to Meraki ILP to avoid issues discovering instances.|
|Fixed a bug that did not adjust the URL to HTTPS when port 443 is assigned via host property.|
|Fixed bugs related to type casting and safe navigation.|
|Added overview graphs.|
|Changed network traffic datapoints to gauge type. Added new datapoints for memory utilization, made graph improvements and other minor fixes, and updated Netscan with expanded capabilities.|
|Updated to raise error alert when no data is received on two consecutive polls indicating there is an API wide data collection issue affecting all monitored devices.|
|Removed health related datapoints to move to module dedicated to health metrics. Historical data will be lost, however these modules were only released at the beginning of November 2022, so there is not much historical data present.|
|Updated the active discovery script available in the support page to allow customers to use a comma-separated list in host property linux.ssh.services to enable automatic discovery of select services. For more information, see Linux (via SSH) Monitoring.|
|Updated to check for our latest snippet loader which adds additional constraints around how many times a request for snippet updates can be made when a previous request failed, and minor updates to display name and tags.|
|Fixed a bug in print message for API errors.|
|Added CPU utilization datapoint with graphs and alerts.|
|Added Azure VM Availability and MemoryAvailable and CPU Credits Consumed/CPU Credits Remaining datapoints.|
|Added DeadLetter metrics.|
|Updated display name to be consistent with other modules in the package — “Office365 Teams Calls QoS”.|
|Updated module to monitor health (Packet Loss (%), Jitter (ms), latency (ms)) for IPSEC tunnels.|
For related module updates, see New LogicModules.
|Improved error messages and added an alternative way to get shared policy sync status.|
|Added encoding of ‘+’ character for alias and description ILPs to ensure proper characters available in UI. Note that the wild alias used for instance naming is unaltered, only the ILP associated with it, therefore instance persistence will not be affected by this change.|
|Updated appliesTo statement to correctly handle MongoDB servers.|
|Added multiple bridge MAC threshold to prevent bridge leakage and more support for SNMP v3. Added CDP and LLDP properties. Extended mapping for ISIS devices.|
|Added fallback for sysname to use display name when sysname is not available.|
|Extended property and topology mapping for ISIS and Cisco ISIS devices.|
|Added Palo Alto and Juniper to manufacturer list for additional properties from 220.127.116.11.18.104.22.168.1.1.1 OID. Also added a new host property deviceBasicInfo.entPhysical.enable to allow manually forcing a device to attempt to add additional properties. Verifying SNMP walk to this OID prior to enabling is recommended.|
|Fixed a bug that caused values containing = to be substituted with -. Fixed a bug in handling of manually added instances.|
|Added multiple bridge MAC threshold to prevent bridge leakage and more support for SNMP v3. Added support for mapInterfaceBridges.|
|Added null safe fix for devices without sysinfo property populated.|
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.
Manual Mapping in Topology Saved Maps
You can now create custom topology edges and connections between two resource nodes which have ERI property set. This feature is currently in Beta.
You can access this feature by enabling the Manual Mapping toggle on the Saved Maps page. When you hover near a resource node, use the cursor to select the node and drag it towards a target node. An arrow will be displayed and you can add details into the Add Connections dialog. The created edge is global and can be viewed anyplace else you have permissions to view in Topology Maps.
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.