v.180 Release Notes

Feature Highlights

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:

• Application Topology Overview
• Application Topology Map
• Application Topology Table

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.

General Updates

Account Settings

Enhancements

• 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

Enhancements

• 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.

Cloud Monitoring

Enhancements

• Updated Microsoft Azure monitoring for VM availability and memory usage. For more information, see Updated LogicModules.

Fixed Issues

• Updated the PostgreSQLFlexible datasource to show BackupStorageUsed metric with the correct update time of five minutes.

Collector

Enhancements

• 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.

Exchange

Enhancements

• When creating datasources, you can now use decimal numbers in the alert threshold expression field and choose field preservation for a wild value field.

Integrations

Fixed Issues

• Expanded support for custom HTTP Integrations to now accept Accept null and valid charsets with valid MIME type in header content-type for integrations.

Logs

Enhancements

• 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 Issues

• 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.

REST API

Enhancements

• 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.

Topology

Enhancements

• You can now delete saved maps in the Topology Maps table, if you have the appropriate roles and permissions for this action.

Fixed Issues

• Interface mapping labels previously displayed the datasource name before the interface label, making it difficult to read the interface name. 

LogicModule Releases

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 LogicModules

Updated LogicModules

Looking Ahead

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.