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.

v.149 Release

v.149 of the LogicMonitor portal is scheduled to roll out to customers from March 8 through March 17.

General Enhancements and Fixes

Alerting

• (FIX) Addressed several issues related to initiating SDT from the Alerts page:
  • Fixed issue preventing SDT in durations of weeks, months, or years from being scheduled.
  • Fixed issue preventing the SDT icon from being immediately shown after setting SDT for an alert.
  • Fixed issue preventing SDT initiation for the device associated with an alert.
  • Attempting to initiate SDT from the old Alerts page UI (available by transforming “/alerts” to “/alert” in the URL) was causing a blank page to be generated. This has been fixed and SDT can now be initiated from the previous UI version of the Alerts page.

• (FIX) Improved warning message when acknowledging a previously acknowledged alert. When acknowledging an alert that was previously acknowledged, LogicMonitor now displays a descriptive warning message:  “Alert <ID> has already been acknowledged”. Previously, the warning consisted of a 400 error.

Audit Logs

• (FIX) Unnecessarily capturing unchanged static thresholds. Previously, LogicMonitor’s Audit Logs were unnecessarily capturing unchanged static threshold data when dynamic threshold data was updated at the resource group level. This has been fixed and Audit Logs now only capture details of dynamic threshold updates.

Cloud Monitoring

• (FIX) Microsoft Azure. The Azure File Storage Capacity was not triggering an alert because the allowed delay time limit was too short. This delay time has been increased (default 2 hours). Added GCC configurations: azure.collector.allowedDelay and azure.allowedDelay.collectionTypes.
• (FIX) Microsoft Azure. Added subscriptionId as additional argument to string.format() to fix an issue where Azure Advisor EventSource was not working.

Collectors

• EA 29.106. Collector version EA 29.106 was released on February 10. This version fixes the known issue present in versions 29.101 through 29.105 that caused resources with heartbeats to be incorrectly marked as dead/down.

Collector releases are deployed independently of LogicMonitor platform releases. For more information on the different Collector versions available for upgrade, see Collector Versions.

LM Logs

• (NEW) Added RBAC support! New Logs permissions for: viewing logs, viewing pipelines, and managing pipelines are now available within roles. You may find this useful for controlling which users can see which logs, and who can create alert conditions. To view logs, a user also needs access to the resources the logs are associated with.

Note: Users who don’t have access to all resources will only be able to view logs for up to 300 resources when no filters are used on the Logs page. This will be fixed in an upcoming release. To avoid this, use at least one filter as a workaround.

• (HOTFIX) Some customers were unable to Add Role when LM Logs was disabled. A fix for this has been deployed.
• (NEW) Multiple resource selection in Pipelines. You’re now able to select more than one resource when creating pipelines.
• (NEW) Two new resource group filtering options were added to the Logs page, allowing you to (1) filter logs associated with resources directly in the selected group and (2) filter logs associated with resources in the selected group AND its subgroups. These filters may be useful for displaying desired logs more efficiently.
• (ENHANCEMENT) Log Alerts. Consistent with other alert types, users can now un-acknowledge log alerts.
• (ENHANCEMENT) Log Alerts. Removed the option to create log alerts from a row in the logs table if at least one log processing pipeline does not exist, because alert conditions are created within pipelines.

Dashboards

• (FIX) NetFlow widget. Previously, the NetFlow widget only displayed the top 10 flows, regardless of the number specified (10, 20, 50 or 100) when configuring the widget. This has been fixed.
• (FIX) Top Applications pie chart not properly rendering on dashboard. Previously, when the Top Applications pie chart was added as a widget to a dashboard (from the Traffic tab), the pie chart remained static, only displayed a solid circle at 100%. This issue has been fixed and the pie chart now correctly displays percentage segmentations when viewed from a dashboard.

Kubernetes

• (FIX) Argus v5 was crashing in some cases following API rate limiting. This has been fixed.
• (ENHANCEMENT) Added Kubernetes Monitoring support for Kubernetes 1.20.

Netflow Traffic Monitoring

• (ENHANCEMENT) Improved support for Cisco ASA devices. Previously, some Cisco ASA devices were not showing network traffic flow data. To resolve this issue, LogicMonitor now accepts alternative initiator and responder fields from the ASA flows to fulfill field requirements.

Important: Collector version 29.107 or higher is required for this enhancement; 29.107 has not yet been released.

Resources

• (NEW) New system.hoststatus property. A new auto-assigned system information property named system.hoststatus has been added for all on-premises devices (it is not applicable to cloud resources). This property updates the status of the device every two minutes. Valid values for this property are:
  • normal – device and associated Collector host are both up
  • dead-collector – device’s associated Collector host is down device and Collector host are both down
  • dead – device is down and associated Collector host is up

Reporting

• (FIX) Alerts report. Log alerts weren’t being reflected in the output of the Alerts report. This has been fixed.
• (FIX) Email notification of report generation failure. When LogicMonitor determines that a report will take a long time to generate, the user is notified that results will be delivered via email. However, if the report were to subsequently encounter an error, users were not being notified via email that generation had failed. This has been fixed. 
• (FIX) Resource Metric Trends report. Two updates have been made to the Resource Metric Trends report:
  • Duplicate graph lines. Previously, this report created duplicate graph lines if duplicate datapoints were present. To resolve this issue, instance checks are now performed while generating graphs and identified duplicate datapoints are treated as a single datapoint with a single plotting.
  • Differing timestamp formats. Previously, the timestamps that displayed when hovering over a point on the graph featured differing formats depending on the duration of the reporting period. This has been fixed and all timestamps are now uniformly formatted.

REST API

• (ENHANCEMENT) More precise error messages for appliesTo field updates. Previously, if a request to update the appliesTo field was made by a read-only user and an incorrect value for the logicModuleId field was provided, the response generated was “Unknown error.” This has been fixed and responses now precisely detail the reason for the error.
• (ENHANCEMENT) More precise error messages for “Invalid json body” errors. The general error response message of “Invalid json body” has been enhanced to additionally include information about the cause of the exception.
• (FIX) Incorrect value returned for the enableFailOverOnCollectorDevice field when Collector is a member of an ABCG. Previously, the API response provided by a request to the  /setting/collector/collectors/{id} endpoint would return the incorrect value of “false” for the enableFailOverOnCollectorDevice field when the Collector was part of an ABCG (Auto-Balanced Collector Group). This has been fixed and the value of “true” is now returned in this case.

User Interface

• (FIX) Pagination preservation. Previously, pagination on the Alerts page was sticky. This has been fixed and pagination is now appropriately reset once you navigate away from the Alerts page.
• (ENHANCEMENT) Topology Mapping. Updated map icons and hover behavior to be consistent with new UI.

User Management

• (FIX) Permissions for Big Number widget on dashboards. Big Number widget (including resourceCount metrics) should be visible for users with Manage permissions on Dashboard and View permissions on the Resources.

New, Updated, and Deprecated LogicModules

New LogicModules

Updated LogicModules

Deprecated LogicModules

LogicMonitor deprecates LogicModules when we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there may be times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any immediate data loss due to the name variation that LogicMonitor expressly adds. However, there will be a diversion in data collection between the deprecated and new LogicModule, and you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable monitoring of the DataSource instances at the resource or resource group level after you have imported its replacement. When DataSource monitoring is disabled in this way, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSource altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSource monitoring, see Disabling Monitoring for a DataSource or Instance.

Entering Beta

Alert Grouping with New Header Graph on Alerts Page

Recently released as a beta feature in v.148 for all Enterprise and Enterprise MSP customer accounts, the Alerts page incorporates a brand new time-series header graph that provides immediate visual insight into an alert storm or other event requiring investigation.

Beta for this new header graph will continue in v.149 as we make performance improvements and align the graph filters with the Alerts page filters.

For more information on using this new alert header graph, see Managing Alerts from the Alerts Page.

Push Metrics API

LogicMonitor is developing a Push Metric API in order to allow metrics to be sent directly to LogicMonitor without the use of a Collector. 

The first phase of the beta, which consists of a REST API that features endpoints for metric ingestion, has been ongoing since early January. The second phase of the beta, which we opened up in early February and includes the addition of a Python SDK, is continuing as well.

If you are interested in participating in the first phase and would like to expand your testing to include the new Python SDK, see the Push Metrics API Solution guide. If you are not currently participating in the first phase, please complete the Customer Beta survey and use the comments section to indicate your interest in participating in testing for the Push Metrics API Python SDK.

Looking ahead: Sunset of RPC API

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

v.148 Release

v.148 of the LogicMonitor portal is scheduled to roll out to customers from February 17 through March 1.

Feature Highlight: Log Alerting

You can now generate alerts automatically on logs!

This release introduces a new concept called Pipelines, which are used to define filters and processing steps on logs as they are ingested. Pipelines are currently scoped to match one resource, but we’ll expand this scope with an upcoming release.

• Add a pipeline to filter logs from resources you always want to track. Manage pipelines in the new Logs > Pipelines page. See Log Processing Pipelines.

The first processing step lets you add alert conditions using regular expressions to match the logs in a pipeline.

• Create alerts directly from any log event or anomaly listed in the Logs page or from a configured Pipeline. Manage alerts from Logs > Pipelines > Pipeline alerts. See Log Alert Conditions.

When log alerts conditions are matched, they trigger standard LogicMonitor alert notifications based on the alert settings (critical, warning, error). You can also view the log alert in the Logs graph, where it will display as a line alongside the alerting log event, and acknowledge the alert in the log list.

You may find this new functionality useful for making logs more actionable, and automating the process of notifying someone when known issues occur.

General Enhancements and Fixes

Alerting

• (FIX) Dynamic thresholds display on Alert Tuning tab. Previously, dynamic thresholds set at the resource group and DataSource levels were not displaying on Alert Tuning tabs. These inherited thresholds are now displayed appropriately in the Dynamic Threshold column, consistent with how inherited static thresholds display in the Static Threshold column.
• (FIX) SDT icon displaying for future SDT time window. On the Alerts page, alerts associated with resources/instances with scheduled downtime (SDT) for a future time window were erroneously displaying the SDT icon for a brief period of time after being selected. This has been fixed and alerts will now only display the SDT icon when the SDT is currently active.

Collectors

• EA 29.106. Collector version EA 29.106 was released on February 10. This version fixes the known issue present in versions 29.101 through 29.105 that was resulting in resources with heartbeats to be incorrectly marked as dead/down. Collector releases are deployed independently of LogicMonitor platform releases. For more information on the various Collector versions available for upgrade and the differences between EA (early access), GD (general deployment), and MGD (minimum general deployment) versions, see Collector Versions.

LM Logs

• (FIX) Timeout issue preventing log display. Previously, a timeout issue was preventing the Logs page from displaying larger numbers of logs as a result of longer time range filters. This has been fixed.

Reporting

• (ENHANCEMENT) More secure report URLs. Reports generated by LogicMonitor (either manually or scheduled) are accessible via a short link URL for a configurable period of time. Previously, the short link URL to access the report consisted of five characters. Conceivably, an attacker could brute-force this value to retrieve and access unexpired links. To safeguard report URLs from being guessed through brute force, report URLs now incorporate 17-character strings that are created by base62-encoding randomly generated 96-bit numbers.
• (ENHANCEMENT) Interface Bandwidth report. The Interface Bandwidth report now features a new Scale by units of 1024 checkbox. (By default, this report is scaled by units of 1000.)

REST API

• (Enhancement) Users with read-only privileges for LogicModules prohibited from passing any values to AppliesTo logic. Previously, users with read-only privileges for LogicModules were able to pass anything to AppliesTo logic. These users are now restricted to default values only when making updates in AppliesTo logic.

Topology Mapping

• Edge filter available when viewing topology maps from the Alerts page. When viewing topology maps associated with alerts from the Maps tab of the alert detail pane, you can now filter the maps by edges. Edge filtering is activated by selecting it as a filter from the dropdown of the funnel icon. When activated, deselected edge types will be removed from the topology map along with any unfocused nodes that are connected to them. Edge filters are not persisted and will reset upon page refresh, tab change, or other context change. The ability to remove edges and nodes that are not relevant can aid in faster troubleshooting.
• Access to relevant, previously-saved topology maps from the Alerts page. When viewing topology maps associated with alerts from the Maps tab of the alert detail pane, you are now able to access and display saved topology maps that incorporate the alerts’ triggering resources/instances. Use the dropdown, initially named after the alert ID, to select a saved map. If the dropdown is disabled, no relevant saved topology maps are available.

User Interface

• (FIX) Payment method edits. An “Unknown error” exception was occurring when attempting to edit the payment method listed in the platform’s financial settings (Settings | Account Information | Financial). This has been fixed.
• (FIX) Erroneous redirect on Resources page. Previously, when selecting the Manage Alert Tuning option for a DataSource listed in the Graphs tab for a selected resource, the user was not being appropriately directed to the Alert Tuning tab for the DataSource. This has been fixed.

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.

New LogicModules

Updated LogicModules

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there are times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any immediate data loss due to the name variation that LogicMonitor expressly adds. However, there will be a diversion in data collection between the deprecated and new LogicModule, and you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable monitoring of the DataSource instances at the resource or resource group level after you have imported its replacement. When DataSource monitoring is disabled in this way, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSource altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSource monitoring, see Disabling Monitoring for a DataSource or Instance.

Entering Beta

Python SDK for Push Metrics API

LogicMonitor is developing a Push Metric API in order to allow metrics to be sent directly to LogicMonitor without the use of a Collector.

The first phase of the beta is continuing and we are now opening up the second phase of the beta which features a Python SDK for the Push Metrics API.

If you are currently participating in the first phase and would like to expand your testing to include the new Python SDK, see the Push Metrics API Solution guide (this guide will be updated shortly with SDK details).

If you are not currently participating in the first phase, please complete the Customer Beta survey and use the comments section to indicate your interest in participating in testing for the Push Metrics API Python SDK.

Easy Alert Grouping with New Header Graph on Alerts Page

Available as a beta feature for all Enterprise and Enterprise MSP customer accounts, the Alerts page incorporates a brand new time-series header graph that provides immediate visual insight into an alert storm or other event requiring investigation.

Mirroring the alerts currently displayed in the alert table, this graph’s aggregated alert counts can be grouped by a number of dimensions including alert severity, associated alert triggers (resource, LogicModule, instance, datapoint), matching alert rules, or the escalations chains used to deliver alert notifications.

Available by clicking the more options icon located in the upper right corner of the Alerts page, the header graph is highly interactive, allowing you to zoom in on a time range or use the graph’s legend to quickly include/exclude a group of alerts. As you interactively change the graph’s filters, the alert table will automatically update to remain in sync.

Note: As a beta feature, this header graph may exhibit some performance or functional issues; closing the graph will eliminate any potential impacts you experience when using other aspects of the Alerts page.

For more information on using this new alert header graph, see Managing Alerts from the Alerts Page.

In the following months, LogicMonitor will continue enhancing alert grouping capabilities with the addition of treemap graphs for subgrouping and new grouping dimensions.

v.147 Release

General Enhancements and Fixes

Alerting

• New “Suppression Type” alert filter. A new alert filter (and alert table column) provides visibility into alerts whose notifications are suppressed by LogicMonitor for the purpose of reducing unnecessary alert noise. The new filter allows you to organize alerts according to the reason behind notification suppression. There are five available suppression types that can be used as filter criteria:
  • None. Returns alerts whose notifications have not been suppressed. (Note: Refrain from using the None filter criterion as it is not working as intended. This is a known issue that will be addressed in an upcoming release.)
  • SDT. Returns alerts whose notifications have been suppressed due to scheduled downtime (SDT) of the triggering resource/instance.
  • Host Down. Returns alerts whose notifications have been suppressed because the Collector has not been able to access the triggering resource (host) for a period of six minutes or more.
  • Cluster Alert. Returns alerts whose notifications have been suppressed because the triggering resources/datapoints are members of a cluster alert and the cluster alert has been configured to supersede the individual alerts.
  • Collector Down. Returns alerts whose notifications were suppressed as a result of being triggered by devices impacted by a down Collector.
  • Anomaly Detection. Returns alerts whose notifications were suppressed as a result of being determined non-anomalous by LogicMonitor’s dynamic thresholds.

  Note: To include the accompanying suppression column in your alert table, you’ll need to customize the column settings for your alert table. To learn more about filtering alerts and customizing alert table settings on the Alerts page, see Managing Alerts from the Alerts Page.

• (FIX) Alert notification sound not playing. In the prior version of the Alerts page, which is accessible by removing the “s” from the very end of the Alerts page URL (transforming “/alerts” to “/alert”), alert sounds were not playing upon arrival of alerts. This issue has been fixed.
• (FIX) Error on opening anomaly detection version of graph from Alerts page. Previously, when attempting to open the anomaly detection version of a graph from the Graphs tab that displays in an alert detail summary, an error was returned. This has been fixed.
• (FIX) Alert clear notifications not delivered during SDT. Previously, LogicMonitor would only deliver alert clear notifications during scheduled downtime (SDT) if alert creation time occurred before SDT start time. Now, alert clear notifications will be delivered during SDT regardless of alert creation time.
• (FIX) Alerts erroneously referencing dynamic threshold as trigger. Previously, alerts generated by static datapoint thresholds with a Delta operator were referencing dynamic thresholds as trigger if dynamic thresholds were also configured for the datapoint. This issue has been fixed.

Audit Logs

• Capturing dynamic threshold updates at resource group/instance levels. LogicMonitor’s Audit Logs now comprehensively capture updates made to dynamic thresholds at the resource group/instance level (from the Resources page).

Cloud Monitoring

• AWS updates:
  • Discovery improvements for AWS SQS. Previously, AWS did not support pagination and only returned the first 1000 Simple Queue Service (SQS) resources. An update from AWS now allows LogicMonitor to discover SQS resources beyond the initial 1000 SQS resources. Note: If you have more than 1000 SQS resources, this discovery improvement could result in an increase in the number of billable cloud resources.
  • New system properties for monitoring AWS RDS. LogicMonitor now sets four new system properties for AWS Relational Database Service (RDS) resources for the purpose of limiting data collection to RDS instances with Performance Insights enabled. These properties are:
    • system.aws.performanceInsightsEnabled
    • system.aws.performanceInsightsKMSKeyId
    • system.aws.performanceInsightsRetentionPeriod
    • system.aws.dbiResourceId

Kubernetes Monitoring

• New Argus version available. The new v5.0.0 version of Argus is now available. As with all major Argus version releases, opt-in is required. See Upgrading Kubernetes Monitoring Applications for upgrade details and enhancements featured in this new version.

LM Logs

• (FIX) Intermittent log visibility on Logs page. Fixed an issue that was preventing the display of new logs on the Logs page, even upon page refresh.
• (FIX) ELB logs incorrectly mapped to LM resources. Fixed an issue that was preventing correct mapping of ELB logs forwarded from sub-directories in an S3 bucket.

Network Traffic Flow Monitoring

• NetFlow Health widget. The Traffic tab now displays an expandable/collapsible widget that provides network traffic flow monitoring health at a glance. This widget highlights the status of several key network flow markers and graphs the last 60 minutes of network traffic monitoring activity.

  Because there is not always an obvious sign that network traffic flow monitoring has been diminished or interrupted, this new widget will serve to provide an earlier warning for time sync issues or high volumes of malformed templates or flows.

  

  Note: This widget requires Collector version 30.100 or greater. Because this version is not yet available, the widget will be auto-collapsed upon release.

Reporting

• (FIX) Dynamic threshold settings not reported. Previously, dynamic thresholds configured for datapoints were not displaying in the output of the Alerts Thresholds report (or on the Alert Tuning tab). This issue has been fixed.
• (FIX) Resource Metric Trends report. In some cases, the Resource Metric Trends report was including negative values on its y-axis scale—even when all reported datapoint values were positive. This issue has been fixed.
• (FIX) NetFlow Device Metric report. IPv6 resolved DNS hostnames now display in the NetFlow Device Metric report.

Topology Mapping

• (FIX) Higher-priority ERTs not assigned. Previously, a higher-priority External Resource Type (ERT) would not be set on a device if a lower, different category ERT was present. This issue has been fixed.

User Interface

• (FIX) Erroneous display of dynamic threshold usage warning upon login. Previously, LogicMonitor erroneously displayed a warning message upon portal login that the allowed limit for configured dynamic thresholds had been exceeded. This issue has been fixed.
• (FIX) Missing note prompt when updating static datapoint thresholds at resource group/instance level. Upon removing, adding, or updating static datapoint thresholds at the resource group or instance level (from the Resources page), users were no longer being allowed to add notes to accompany the action for display in the static threshold history. This ability had been inadvertently removed in a previous version, but has now been returned.

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.

New LogicModules

Updated LogicModules

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there are times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any immediate data loss due to the name variation that LogicMonitor expressly adds. However, there will be a diversion in data collection between the deprecated and new LogicModule, and you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable monitoring of the DataSource instances at the resource or resource group level after you have imported its replacement. When DataSource monitoring is disabled in this way, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSource altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSource monitoring, see Disabling Monitoring for a DataSource or Instance.

Entering Beta

Push Metrics API

LogicMonitor is developing a Push Metric API in order to allow metrics to be sent directly to LogicMonitor without the use of a Collector. Some technology landscapes where this capability is becoming vital include server-less infrastructures such as AWS Lambda, large distributed microservices environments with custom metrics (including business metrics), and IoT environments.

The first phase of beta for Push Metrics API is underway! In this first beta phase, a REST API is provided for beta participants that features endpoints for metric ingestion, resource property update, and instance property update.

In the second beta phase (targeted for the later half of Q1 2021), the REST API and a Python SDK will additionally be available for beta participants. We plan on making other language-specific SDKs available soon after.

If you have a compelling use case and the resource availability, and would like to be considered for participation in either the first or second beta phase, please complete the Customer Beta survey. In the comments section please let us know if you would like to use the REST API directly, via Python SDK, or have a request of another language-specific SDK such as Go, Java, or .NET.

Cloud Integrations in LM Exchange

In this beta release, we’ve made some cloud integrations available through LM Exchange in your LogicMonitor portal. LM Exchange will make it possible for you to sort and filter for modules by type or status, for example, to see when upgrades are available or to review all the LogicModules available in a package.

Specifically, for this beta, the AWS cloud integration onboarding has received a facelift and can now be initiated from LM Exchange. Microsoft Azure and GCP will follow suit in future releases.

Also, as part of this beta, we are beginning our SaaS API authentication for Office365—with more SaaS solutions (Zoom, SalesForce, and so on) to follow in coming releases. This marks a new method for agentless collection of SaaS application metrics.

If you are interested in participating in the beta program for SaaS integrations, reach out to your LogicMonitor representative. Ideal partners are already leveraging cloud monitoring and are willing and able to integrate with at least one Office 365 subscription and participate in feedback rounds.

v.146 Release

IMPORTANT: Beginning with the rollout of v.146, LogicMonitor is updating its new version deployment window to 7:30-10:30 p.m. PT (previously, the window was 6-9 p.m PT). We will continue to provide in-app notification 48 hours in advance of a new version deployment.

General Enhancements and Fixes

Alerting

• Ability to link alert to its associated components. The alert detail pane now provides hyperlinks to the resource/website/service associated with the alert and the DataSource (if applicable).
• (FIX) Alert acknowledgement. Resolved an issue that was causing exceptions when users with a particular combination of permissions attempted to acknowledge alerts.
• (FIX) Cleared ConfigSource alerts. Fixed issue preventing cleared alerts triggered by ConfigSources from displaying in the Alerts page.
• (FIX) Time zones in graph legends. Resolved issue where graph legends (as displayed on the Graphs tab of the alert detail pane) were not honoring the user’s configured time zone.
• (FIX) Severity icon display. Resolved an issue preventing the display of severity icons in some cases when viewing the pop-out version of an alert from the Alerts page.

Cloud Monitoring

• AWS updates:
  • AWS Bahrain region added. Added support for the AWS Bahrain region (me-south-1), which is the first AWS region in the Middle East. Customers can now monitor services in the Bahrain region that are supported by LogicMonitor’s AWS monitoring.
  • New StorageType property for AWS RDS. Added StorageType as a property for AWS Relational Database Service (RDS). This new property (system.aws.storageType) allows logical grouping and filtering according to StorageType.
  • (FIX) AWS Kinesis Streams permissions. Previously, AWS Kinesis Streams permissions were not being properly tested. In some cases, this resulted in customers not being alerted that additional permissions were required to be able to monitor AWS Kinesis Streams from the LogicMonitor portal. This issue has been resolved.

Dashboards

• Alert List widget. The behavior of the anomaly filter available in the alert list widget configurations now aligns with that of the anomaly filter available on the Alerts page.
• (FIX) Custom Graph widget. The Custom Graph widget was returning an “invalid virtual datapoint expression” error when attempting to calculate virtual datapoints that referenced datapoints belonging to the same DataSource, but applying to different resources. This issue has been resolved. If you previously experienced this issue, open the Custom Graph widget configuration dialog and simply save the current configurations – no edits are necessary.
• (FIX) Rounding of Y-axis values. In some cases, the Y-axis value for some graphs was not displaying as a rounded value. This issue has largely been resolved, although there is still a remaining corner case that we are actively working on where non-rounded values still display if display type is selected as “Line” and data is constant (data is displayed in a straight line) for virtual datapoints

Kubernetes Monitoring

The following new features and improvements will be available with the new v5.0.0 version of Argus, which is targeted for arrival in early January.

• Avoiding name conflicts in discovery. To avoid name conflicts and subsequent issues with discovery, the following enhancements were made:
  • Resource type (for example, “Pod”) is appended by default to the LogicMontior display name
  • New Argus Helm chart options, FullDisplayNameIncludeNamespace and FullDisplayNameIncludeClusterName, are available to append namespace and cluster name respectively to the LogicMonitor display name (default: false). You may find that enabling one of these two new options is useful for avoiding naming conflicts in cases where pods with the same names are running across multiple namespaces and/or clusters.
  • For resources that fail to be added due to name conflicts, the conflicting resource will be added to a dynamic group named “_conflicts”.
• Discovery filtering by pod name. Pod name is now available for use with discovery filtering, including handling of special characters such as hyphens. You may find this useful for filtering pods in/out of monitoring based on names rather than labels.
• Discovering EKS Fargate nodes and pods. Previously, nodes and pods for EKS Fargate weren’t being discovered properly due to shared IPs, but no host network specification in the pod manifests (EKS Fargate pods each run on a distinct node and share IPs, but don’t use the Kubernetes Host Network specification). To account for this, we’re now categorizing pods with the EKS Fargate label “eks.amazonaws.com/fargate-profile” as pods configured with host networking. This will ensure (1) the right value for the system.hostname property gets set, (2) the right DataSources apply, and, most importantly, (3) there are no discovery conflicts between pods and nodes for EKS Fargate.

LM Exchange

• New LogicModule statuses. LogicModule statuses “Beta” and “Deprecated” now display in the LogicModule metadata table.

LM Logs

• Log events +/- three hours no longer accepted. Log events with timestamps more than three hours in the past or future are no longer accepted, and will result in a new 4006 API response code. This is to ensure relevance of data and protect against misconfigured timestamp settings.

Network Traffic Flow Monitoring

• New benchmarks. New capacity benchmarks for network traffic flow have been published for the Large, XL, and XXL Collectors. These benchmarks show a dramatic increase in the number of flows per second that can be comfortably monitored and were reached as a result of an ongoing initiative to enhance and optimize LogicMonitor’s network traffic flow monitoring capabilities. See Collector Capacity for the new benchmarks.
• Support for sFlow version 5. Added support for sFlow version 5 (Collector version 29.105 or higher is required).
• DNS lookups. Increased the DNS cache storage duration to 24 hours (previously duration was 30 minutes) to resolve repeated DNS queries preventing the resolved names from displaying.
• (FIX) IPv6 address format display. Normalized IPv6 address format display for NetFlow IPv6 endpoints that do not resolve via DNS.

REST API

• (FIX) Locked API tokens. Previously, locked API tokens due to multiple unsuccessful authentication attempts were causing an exception to occur. This issue has been resolved.
• (FIX) Updating a device via PATCH request. Previously, submitting a PATCH request to modify both a device “name” and its customProperties would result in the device name updating to the name of one of the customProperties. This issue has been resolved.
• (FIX) /apiStats/externalApis. Previously, /apiStats/externalApis was returning separate values for API calls to the same endpoint depending on whether the user made the call with or without a trailing forward slash (/). This has been corrected and calls with either variation are now appropriately identified and aggregated as a single entry in the response.

Website Monitoring

• New Web Check properties. Several new properties are now available for manipulating the settings of Web Checks. Specifically, these settings provide some flexibility in cases where sites may load slower than the default timeouts used by LogicMonitor’s external checkpoints.

  The following built-in properties all default to 30 seconds and all support an acceptable value range between >0 and <=60.

  • website.http.client.so.timeoutInSec (socket timeout in seconds)
  • website.http.client.connect.timeoutInSec (TCP connection timeout in seconds)
  • website.http.client.read.timeoutInSec (read timeout in seconds)

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.

New LogicModules

Updated LogicModules

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there are times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any immediate data loss due to the name variation that LogicMonitor expressly adds. However, there will be a diversion in data collection between the deprecated and new LogicModule, and you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable monitoring of the DataSource instances at the resource or resource group level after you have imported its replacement. When DataSource monitoring is disabled in this way, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSource altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSource monitoring, see Disabling Monitoring for a DataSource or Instance.

Entering Beta: Push Metrics API

LogicMonitor is developing a Push Metric API in order to allow metrics to be sent directly to LogicMonitor without the use of a Collector. Some technology landscapes where this capability is becoming vital include server-less infrastructures such as AWS Lambda, large distributed microservices environments with custom metrics (including business metrics), and IoT environments.

Beta for Push Metrics API is targeted for January. If you have a compelling use case and the resource availability, and would like to be considered for participation, please complete the Customer Beta survey.

v.145 Release

General Enhancements and Fixes

Alerting

• Bulk alert acknowledgement. The new UIv4.1 version of the Alerts page, rolled out in v.143, now supports the ability to acknowledge multiple alerts at once.
• Dynamic threshold usage limit. The usage limit calculation for dynamic thresholds has been updated to use the contracted resourced count rather than the current resource count. The new calculation (contracted resource count * 8) more accurately (and consistently) reflects dynamic threshold usage limits.
• (FIX) Alert overview graphs. Customers without access to the dynamic thresholds feature were receiving permissions errors when attempting to view the overview graph that displays as part of the Overview tab of an alert’s detail view (found on the Alerts page). To resolve this issue, overview graphs will no longer attempt to load expected ranges in portals where dynamic thresholds are not supported.
• (FIX) Detail URL for cleared alerts. When opening the detail views for cleared alerts in new browser tabs—either from the LogicMonitor interface or from delivered alert notifications that incorporate the ##ALERTDETAILURL## token—the resulting web pages were opening as blank pages. This has been fixed.

Cloud Monitoring

• AWS updates:
  • AWS Africa region added. Added support for the AWS Africa region (af-south-1), which is the first AWS region in Africa. Customers can now monitor services in the AWS Africa region that are supported by LogicMonitor’s AWS monitoring.
  • Updated AWS Direct Connect connection state mapping. AWS Direct Connect is changing from a “default to unavailable” to a “default to available” for monitoring. There remain two connection states for removing instances (“Deleting” and “Deleted”) and three connection states that are unavailable for monitoring (“Requesting”, “Ordering” and “Rejected”). Remaining connection states will map to an available state, allowing clients to monitor in LogicMonitor.
  • Using recommended AWS STS methods. LogicMonitor has updated the method it uses to obtain cross-account authorization tokens from AWS Security Token Service (STS). The new method follows AWS’ best practices and will allow for easier future addition of new AWS regions to the LogicMonitor portal. No action is required on the customer’s end.
  • (FIX) AWS Trusted Advisor API. As a result of changes made to the AWS Trusted Advisor API, several DataSources were not associating: AWS_IAM_ServiceLimits, AWS_VPC_TrustedAdvisorServiceLimit, and AWS_EC2_TrustedAdvisorServiceLimits. To resolve this issue, LogicMonitor has updated the method for validating and calling the Trusted Advisor API.
• Azure updates:
  • Name adjustments for Notification Hubs and SQL Elastic Pools services. Previously, when attempting to change the display names of Notification Hubs and SQL Elastic Pools services with forward slashes (/) in their resource names, errors were returned. To resolve this issue, forward slashes found in the names of Notification Hubs and SQL Elastic Pools services will be replaced with colons (:). Note: Only resource names are affected by these changes; forward slashes may still appear in display names, where permitted.
  • (FIX) Billing data calculations. There was an issue in calling cached RateCards to calculate the Azure billing data. This is fixed and should require no action from the clients.

Collectors

• EA 29.104. Collector version EA 29.104 was released on November 10. Collector releases are deployed independently of LogicMonitor platform releases. For more information on the various Collector versions available for upgrade and the differences between EA (early access), GD (general deployment), and MGD (minimum general deployment) versions, see Collector Versions.

Dashboards

• (FIX) NOC widget. Instance-level filters containing OR operations, as formatted with the pipe symbol (|), were not being correctly evaluated, causing a “Resource Not Found” error to be returned by the widget display. This has been fixed.

LM Exchange

• (FIX) LM Locator code display. The LM Locator code was not displaying for installed LogicModules. Impacting the Exchange and Settings pages, this has been fixed.

Network Traffic Flow Monitoring

• (FIX) NBAR2 application type. Application type (as sourced from NBAR2) was not displaying properly in the Traffic Tab visualizations for network traffic flow data. This has been fixed.

Role-Based Access Control

• Improved error handling when acknowledge privileges are missing. More descriptive error messages are now returned when users with SDT-only or threshold-only privileges for a resource attempt to acknowledge alerts triggered by that resource.

New, Updated, and Deprecated LogicModules

Recently released to the LogicMonitor public repository, our new and updated LogicModules are available for import to expand and enhance your monitoring coverage.

New LogicModules

Updated LogicModules

Deprecated LogicModules

LogicMonitor deprecates LogicModules for a variety of reasons. Most often, it is because we have published a replacement LogicModule that provides superior access to the monitored technology (for example, supports more versions of the technology or provides improved scalability).

However, there are times when a LogicModule is deprecated with no replacement (for example, when a technology becomes defunct or security issues beyond LogicMonitor’s control arise).

Note: When importing a replacement LogicModule, you will not experience any immediate data loss due to the name variation that LogicMonitor expressly adds. However, there will be a diversion in data collection between the deprecated and new LogicModule, and you will potentially collect duplicate data and receive duplicate alerts for as long as both LogicModules are active. For this reason, we recommend that you disable monitoring of the DataSource instances at the resource or resource group level after you have imported its replacement. When DataSource monitoring is disabled in this way, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSource altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSource monitoring, see Disabling Monitoring for a DataSource or Instance.

Entering Beta: Push Metrics API

LogicMonitor is developing a Push Metric API in order to allow metrics to be sent directly to LogicMonitor without the use of a Collector. Some technology landscapes where this capability is becoming vital include server-less infrastructures such as AWS Lambda, large distributed microservices environments with custom metrics (including business metrics), and IoT environments.

Beta for Push Metrics API is targeted for January. If you have a compelling use case and the resource availability, and would like to be considered for participation, please complete the Customer Beta survey.