v.159 Release Notes

v.158 Release Notes

v.157 Release Notes

v.156 Release Notes

v.155 Release Notes

v.154 Release Notes

v.153 Release Notes

v.152 Release Notes

LogicMonitor v.152 is scheduled to roll out to customer portals from May 12th to May 24th.

General Updates

Alerts

• ADDED functionality to save header graph selections as part of a “Saved View” for the Alerts page.
• ADDED alert sounds to the Alerts page. You can enable sounds for Critical, Error, and Warning alerts.
• CHANGED the default behavior when resetting time range and filter selection. The time range should be set to “Any Time” and all severity toggles should be enabled.
• FIXED an issue where it wasn’t possible to change the time range to view Anomaly Detection graphs associated with Alerts.
• FIXED issues where Datapoint name was missing or showed “null” in Audit Logs for resource and instance-level changes to Dynamic Thresholds.
• FIXED an issue where Audit Logs included information for datapoints even when they were not updated. The log should only contain information for the dynamic and static thresholds that are changed or updated.

Cloud Monitoring

• ADDED “Test AppliesTo” functionality for Cloud integrations where Local Collectors are applied.
• ADDED capability for users to clear Permissions warnings and errors for Cloud accounts when “Test Permissions” is clicked when managing and adding integrations.
• ADDED access controls to the Cloud Integrations page to display only Cloud and SaaS tiles that users have access to.
• CHANGED the Microsoft Azure configuration options to make the billing country an optional field.
• FIXED an issue in Azure accounts where users could not edit permissions for the account when the secret key expired.
• FIXED an issue where the setting to “automatically delete terminated resources” was not working.

Container Monitoring

• CHANGED the commands for adding the LogicMonitor Helm chart repository to use ‘github.io’ because GitHub has stopped redirecting from ‘github.com’. If you previously added LogicMonitor charts, you will need to re-add the charts with the ‘github.io’ command to avoid future Helm update failures: helm repo add logicmonitor https://logicmonitor.github.io/k8s-helm-charts

LM Collector

• RELEASED GD Collector 30.000 on 29 April 2021. This version incorporates updates and fixes from GD 29.003 and EA 29.xxx versions. See GD Collector 30.000 Release Notes for more information.
• RELEASED EA Collector 30.100 on 20 April 2021. This version adds support for Kubernetes Events and Windows Events Logs collection for LM Logs, new OpenMetrics collection, and more. See EA Collector 30.100 Release Notes for more information.
• ADDED support for all identifiable transmission protocols (beyond TCP and UDP) supported by Netflow and IPFIX.
• FIXED an issue where some sensitive information (such as passwords and API keys) is masked during configuration but not in responses.

LM Exchange

• DEPRECATED the Safe LogicModule Merge (SLM) feature in LM Exchange. SLM will be removed in v.155. This removal is temporary as we continue to update the LM Exchange UI and capabilities, and we plan to reintroduce the functionality in a future release.

LM Integrations

• RELEASED v1.1.0 update for our official Ansible integration. This release includes support for enhanced provisioning functionality and support for auto-balanced collector groups. The certified integration is available now at Automation Hub, and the community version is still available via Ansible Galaxy. See the documentation for the Ansible Integration.
• FIXED an issue where exporting existing HTTP integration would return a 500 error code when the payload format is null or empty. The payload is expected to be one of the following: form data, JSON, plain text, url-encoded form data, or XML. As long as the payload is valid, the integration should export to a JSON file.

LM Logs

• ADDED filters for logs messages based on alert severity (Critical, Error, Warning). The clickable icons are located next to the Raw Logs icon. There will also be an icon on the log messages that generated an alert.
• ADDED a new method for deploying the LM Logs Azure integration. This deployment option streamlines the creation of the Azure Function and Event Hub with a button click, and also provides an easier method for forwarding logs to these new resources. You may find this useful if you are unfamiliar with Terraform or Gradle, which were previously the only deployment options offered.
• FIXED an issue where logs failed to initially load if a user did not have access to all devices and the user would need to select a resource group to see the logs they had access to. This issue has been corrected and logs for all devices a user has access to will be displayed without action required.
• KNOWN ISSUE If you delete an alert condition from a log processing pipeline in LM Logs, the pipeline will not match.

LogicModules

• CHANGED the requirements for Two Factor Authentication to make phone numbers auto-populated and not editable by the user. A notification message will display to 2FA users that they will need to update their phone numbers beginning in the next release.
• FIXED an issue with SSO that prevented users from signing in to all portals if they used the same IDP provider (such as Azure) for multiple portals.

Security

• FIXED an issue where expressions containing parentheses in AppliesTo criteria returned an invalid expression error. This was caused by a check for sensitive properties and has been reverted.
• FIXED issues where some LogicModule datapoints would lose metric names upon import from repository.

Reports

• FIXED issues where Interface names did not appear in Graphs and Reports if they contained double quotes.
• FIXED the sorting behavior of Resource Metric Trends Report.

Resources

• CHANGED the workflow of system.hoststatus property to improve updates for the status of devices (normal, dead, dead-collector).
• FIXED issues where properties that are case insensitive were treated as different properties at different levels. With the exception of system properties, properties are now case insensitive across levels, and if the child property is a different case it will override the parent property. In appliesTo functions, the device will match from the immediate child value of the property.
• FIXED an issue that caused instance-level properties to be overridden in some cases.

REST API

• ADDED a note to the Python SDK documentation. For Python SDKs, the REQUEST parameters can contain camelCase or an underscore. However, the RESPONSE parameters will always contain an underscore. See LogicMonitor SDKs.

RPC API

• FIXED an issue where the getAlerts endpoint was returning “No Data”. See “Sunset of the RPC API”.

User Management

• FIXED an issue where users were not seeing options to “Add dashboard” and “Add dashboard group” when they were assigned the Manage permissions.

Websites

• CHANGED how hashcodes are calculated to improve performance and reduce the gaps displayed in the Website’s graph.
• CHANGED the column length of Website folder names to support up to 255 characters (similar to resource group names).

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 the General Updates section.

New LogicModules

Updated LogicModules

Deprecated LogicModules

This table lists LogicModules which we are deprecating in this release. This means that these LogicModules will be removed in a future release. A replacement LogicModule is listed, if there is one available.

For the list of LogicModules deprecated over the past five releases, see the support article Deprecated 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.

Distributed Tracing enters beta

LogicMonitor’s distributed tracing functionality will be entering beta soon! With this new distributed tracing capability, you will be able to forward traces from your instrumented applications to LogicMonitor. This will enable you to see end to end traces as they flow through the services in your environment (from a new Traces page in LogicMonitor), presented with contextual metrics and logs to enable faster troubleshooting and more proactive identification of performance bottlenecks. 

To participate in this beta, fill out this form: Tracing Beta Survey

Push Metrics API enters beta in production environments

The Push Metrics API is now available for beta participants in production environments, but the feature must be enabled. Prior to enablement we would like to discuss best practices for testing and implementation as well as pricing considerations once the feature is generally available. 

To participate in this beta, fill out this form: Push metrics API Production Beta

OpenMetrics DataSource Wizard enters beta

The OpenMetrics DataSource Wizard beta is available as an open beta in both sandbox and production environments. The wizard requires the EA Collector 30.100 or later. The wizard can be used to quickly load OpenMetrics (Prometheus exposition format) data from a provided URL endpoint and create a datasource for ingesting the data into your LM account. 

To participate in this beta, fill out this form: OpenMetrics Beta Survey

Sunset of the RPC API

We have decided to focus on improving the LogicMonitor Rest API, which has higher security standards and integration capabilities that are more in-line with our future development goals. This means that we are preparing to end support for the RPC API with the upcoming release of LogicMonitor v.156. 

If you are using the RPC API for Ansible, reach out to Support for guidance on migrating playbooks to the REST API.

v.151 Release Notes

LogicMonitor v.151 is scheduled to roll out to customer portals from April 19th through April 28th.

Feature Highlights

Alert Grouping, now with Tree Map Visualization

The new header graph and alert grouping functionality is now generally available on all LogicMonitor accounts. In an earlier version of this feature, the time-series header graph provided immediate visual insight into an alert storm or related events requiring investigation. In this release, we’ve improved the performance of the alert grouping and added a new Tree Map visualization option for the header graph.

The Tree Map graph allows you to select two dimensions when grouping alerts. For example, you can select LogicModule and Resources to get a grouping of all LogicModules that are “in alert” for the given time range, as well as a count of the number of resources with each LogicModule alert. Using the header graph to drill down into a LogicModule will further group the alerts by Resources with that LogicModule alert.

For more information about the alert graph header and alert grouping, see Managing Alerts from the Alerts Page.

General Updates

Alerts

• ADDED Datapoint names to the Audit Log records when changes are made to the Datapoint value in Dynamic Thresholds.
• ADDED an error message if the number of alerts being grouped exceeds the maximum limit of 10,000 alerts.
• CHANGED the column name “Dependency Routing State” to “Notification State” on the Alerts page.
• FIXED an issue in the Alerts page where expanding the Support panel caused it to overlap the workspace. The panel will now “push” the content as it expands, allowing users to see what they are working on as well as the Support information. This fix also applies to modals.
• FIXED an issue in the Alerts page where selecting and deselecting filters changed the total alert count. The total alert count should be the same regardless of filter selection.
• FIXED an issue in the Alerts page where the UI showed time-based thresholds when they didn’t exist.

Cloud Monitoring

• ADDED support for Azure Enterprise Agreement type billing information. To monitor your Azure EA Billing, input your subscription information and import the new DataSources to your portal. (Note: LogicModule updates will be available in an upcoming release.)
• ADDED support for monitoring data from Zoom. Add Zoom to your portal from Exchange > Cloud Integrations. To monitor data from Zoom, you will need to provide a Client ID and Secret Key when setting up the integration, add the resource, and import the Zoom DataSources.

Container Monitoring

• CHANGED the naming of HPA resources to use a combination of name and namespace. Previously, HPA resources were not being added if their system.hostname value were duplicated in the Collector.
• CHANGED the commands for adding the LogicMonitor Helm chart repository. GitHub has stopped redirecting from ‘github.com’ to ‘github.io’. Because of this, we’ve updated the ‘helm repo add’ command in our UI. If you’ve previously added LogicMonitor charts, you will need to run the following command to re-add charts with the ‘github.io’ command to avoid failure of helm updates: helm repo add logicmonitor https://logicmonitor.github.io/k8s-helm-charts

LM Collector

• EA Collector 30.101 will be available in an upcoming release.

LM Logs

• ADDED alerts into the Logs page. Alerts are now viewable in the logs table and header graph.
• ADDED RBAC Logs management for log ingestion. Permissions can be set to specify which users are allowed to send logs to LM Logs.
• FIXED an issue in Pipelines where the regular expression was matching incorrectly and causing the pipeline to not work.

LM Service Insight

• FIXED an issue where delayed data will result in incorrect aggregations and sometimes lead to false alerts. We will show “No Data” for aggregations if we don’t have enough data to avoid this issue.

LogicModules

• CHANGED appliesTo criteria to not allow any sensitive property within functions.

Resources

• FIXED an issue where editing Dynamic Groups would display different error messages if the description was too long and included the keyword “update”. The maximum limit for the description field is 255 characters.

Known Issues

• When inheriting properties, the device will match the child-level property only, so you may see an addition or deletion of resources depending on the case.

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 the General Updates section.

New LogicModules

Updated LogicModules

Deprecated LogicModules

This table lists LogicModules which we are deprecating in this release, this means that these LogicModules will be removed in a future release. A replacement LogicModule is listed, if there is one available.

For the list of LogicModules deprecated over the past five releases, see the support article Deprecated LogicModules.

Looking Ahead

OpenMetrics DataSource Wizard enters beta

The OpenMetric DataSource Wizard will be available on sandbox account environments soon. The wizard requires EA Collector 30.100. The wizard can be used to quickly load OpenMetrics (Prometheus exposition format) from a provided URL endpoint and create a DataSource for ingesting the data into your LogicMonitor account. If you are interested in participating in the beta, please contact your CSM for more information.

Sunset of the RPC API

We have decided to focus on improving the LogicMonitor Rest API, which has higher security standards and integration capabilities that are more in-line with our future development goals. This means that we are preparing to end support for the RPC API with the upcoming release of LogicMonitor v.156. If you are using the RPC API for Ansible, reach out to Support for guidance on migrating playbooks to the REST API.

v.150 Release Notes

LogicMonitor v.150 is scheduled to roll out to customer portals from March 29th through April 7th.

Feature Highlight: New management experience for Cloud and SaaS Integrations

Onboarding and management for Cloud Monitoring have a new look and feel. Changes include updated workflows and embedded documentation to create a more seamless and intuitive onboarding and management experience. You can add new integrations directly from the Exchange tab under Cloud Integrations.

Additionally, we are bringing cloud methodology to SaaS Monitoring by implementing API-based monitoring for all your business needs. You can monitor business critical SaaS’s for usage, availability, consumption, and more. This API approach will start with Microsoft Office 365 and Salesforce in this release, with more integrations to come in future releases. Reach out to your Sales and CSM team for more information.

New SaaS Integrations will also be available from Exchange > Cloud Integrations. Vote for Integrations to help us prioritize upcoming SaaS releases.

General Updates

General Updates describes the changes made to LogicMonitor features in this release.

Alerting

• CHANGED the dynamic thresholds algorithm to improve handling of sparse data. As a result, you may see a gap in alerting and suppression by dynamic thresholds of approximately 5 hours where this new algorithm retrains historical data.
• FIXED an issue where the ##INSTANCEGROUP## token was not populating in the active alert integration payload.
• FIXED an issue with the ServiceNow integration. When you updated the Note field in the Alert details, log alerts were being acknowledged in ServiceNow but not in LM Alerts.
• FIXED an issue where External Ticket ID was not showing in a device Alert tab or Report, even when it was present in integration logs. You may need to manually add an External Ticket ID column to the device’s Alert tab or Report if it is not already added.

Cloud Monitoring

• ADDED Azure SignalR Metrics that are exposed in Azure Monitor: ConnectionCount, InboundTraffic, MessageCount, OutboundTraffic, SystemErrors, UserErrors.
• CHANGED GCP Billing integrations to follow GCP standards. For example, new and existing billing integrations now use BigQuery Table IDs.

Collector Releases

• EA Collector – 29.108 was released on March 11, 2021. This release adds integration support for external credential management using CyberArk Vault. Note: The vault integration is currently an open beta release. For more information, see Credential Vault Integration for the LM Collector.

Kubernetes Monitoring

• ADDED new properties to log Argus versions for better troubleshooting: argus.app-version and argus.app-version.history.
• ADDED a retention period for Argus resources that are removed from monitoring.
  • When you set deleteDevices = true in your Argus Helm deployment, it will automatically set a property kubernetes.resourcedeleteafterduration = 1 day at the group level for your cluster. This setting will retain the resources for 1 day after they are terminated. Terminated resources awaiting deletion are added to a new dynamic group with alerting disabled to avoid alert noise.
  • You can override the value (for how long the resources are retained) by setting this property at the device or sub-group level. The maximum value is 10 days (P10DT0H0M0S).
  • Note: While we recommend LM Service Insight to ensure you retain historical data at the application and service level, this retention option will enable you to get granular historical data for individual resources (such as pods).

LM Config

• FIXED an issue where config alerts were automatically clearing before they were acknowledged if “Clear when acknowledged” was selected.

LM Logs

• FIXED a bug where navigating from Alert graphs to View Logs resulted in a line marked ‘undefined’ on the logs overview graph.
• FIXED a timeout issue that was occurring when searching for certain time periods of logs.

REST API

• The LogicMonitor REST API 2.0.0 documentation was updated on March 18, 2021.

User Interface

• FIXED an issue where the search query and cleared alerts wouldn’t display at the same time in the new Alerts UI.
• FIXED an issue where hostcluster, batchjob, and eventsource alerts were incorrectly labeled as website alerts. 
• FIXED an issue to correct the pagination of the new Alerts page when there are no alerts.

User Management

• FIXED an issue where cloning an existing role would select all Saved Maps groups. It should only apply the selection from the existing role.

Website Monitoring

• FIXED an issue where inheriting and overriding a custom Website property would cause it to display twice because the case in the property didn’t match.

LogicModule Changes

Enhance your monitoring with new and updated LogicModules, which are available for you to import from the LogicMonitor Public Repository.

New LogicModules

Updated LogicModules

Deprecated LogicModules

This table lists LogicModules which we are deprecating in this release, this means that these LogicModules will be removed in a future release. A replacement LogicModule is listed, if there is one available. For the list of LogicModules deprecated over the past five releases, see the support article Deprecated LogicModules.