v.237 Release Notes

LogicMonitor Collector now includes the Weighted Balancing switch on the Add Collector Group page that enables weighted balancing to determine Collector load instead of relying solely on instance count. This enhancement now improves load balancing accuracy by accounting for variations in resource consumption across different data collection types. Collectors now dynamically evaluate their capacity based on the weight of instances per collection type which enables more efficient distribution of instances across Auto-Balanced Collector Groups (ABCGs).

In this approach, each instance is assigned a weight based on multiple factors, including Collector size, supported data collection types, total Collector capacity, current instance count, and maximum instances supported for each data collection type per Collector size. The system calculates the total weight of instances across all data collection types and determines whether a Collector is within capacity or overloaded.

If the total weight exceeds the Collector capacity (that is, 100% capacity), the Collector is considered overloaded and automatically offloads resources to another Collector within the ABCG. This process does not require manual input or threshold configuration.

You can enable either the Weighted Balancing switch or the Property Based Balancing switch. Enabling one switch hides the other switch. If you enable the Weighted Balancing switch, the Collector Status page for that Collector displays the collection types and their corresponding current instance count in the Weighted ABCG Balancing Status section. Since weighted balancing does not require threshold configuration, the Calculated Threshold column is not available on the Collectors page for Collectors with the Weighted Balancing switch enabled.

To access this feature, navigate to Settings > Collectors. Select “Add Collector Group” from the Add Collector Options dropdown menu. On the Add Collector Group page, toggle the Auto Balanced Collector Group switch.

To access the Collector Status page, navigate to Settings > Collectors. Select the Collector with the Weighted Balancing switch enabled. In the Actions column, select More > Collector Status.

For more information, see Auto-Balanced Collector Groups in the product documentation.

Cost Optimization Recommendations now generates recommendations for Azure SQL Databases detected as “idle” for 14 days, increased from seven days. This increased timeframe enhances the accuracy of detecting idle resources, enabling you to determine the best actions to reduce cloud costs.

For more information, see Cost Optimization – Recommendations in product documentation.

You can now create and view monthly budgets for your cloud billing costs in Cost Optimization. This enhancement provides visualizations for monthly spending thresholds you set for cloud resources in Billing, as well as alerts for those thresholds that you can create and customize.

This enables you to monitor regular monthly spending on those cloud resources that matter most, and be notified when cloud costs impact your budget.

To access this feature, navigate to Cost Optimization > Billing and select the Budgets tab. Select Add Budget to create a new budget.

For more information, see Cost Optimization – Billing in product documentation. For more information on budget alerts, see Types of Alerts in LogicMonitor.

You can now configure widget-level filtering in the Big Number widget that operates independently of dashboard-level filters. You can filter by specific resources, instances, and properties to display metrics for a targeted subset of your infrastructure, such as a defined region, environment, or service.

Widget-level filters function separately from dashboard filters. You can apply broader dashboard filters or use drill-down actions without affecting the specific criteria configured for an individual Big Number widget.

To access this feature, navigate to Dashboards and add a Big Number widget.

For more information, see Big Number Widget in the product documentation.

As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed from Dashboards, making Dashboards unavailable using the legacy UI, and available in the new UI only. The new UI provides an enhanced user experience, improved performance, and security features.

For more information about this deprecation, including timeline and further updates about the removal, see Upcoming End-of-Life (EOL) for UIv3 Dashboards in LM Community.

For the most up-to-date information about Dashboards, see Dashboards Overview in the product documentation.

If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.

You can now use the new Action Notes alert status for ConnectWise to update the Notes section of a ConnectWise service ticket with a DiagnosticSource output report in JSON or plain text format.

LogicMonitor now includes the following tokens to configure the payload sent when a DiagnosticSource report is available for an alert:

• ##DIAGNOSTIC_SOURCE_OUTPUT##
• ##DIAGNOSTIC_SOURCE_STATUS##
• ##MESSAGE##

These tokens apply only to the Action Notes alert status for ConnectWise integrations.

For more information, see ConnectWise Integration in the product documentation.

You can now view log properties in a consistent, structured order to improve usability and make it easier to locate related information.

Log properties are now sorted alphabetically, with _lm fields first, followed by other fields. Related fields are grouped together (for example, source_ip and source_dns), improving readability and enabling faster analysis.

You can now bulk delete groups in Shared and Public tabs within Managed Saved Views. This enhancement enables you to remove multiple groups in a single action, improving efficiency when managing saved views.

Additionally, if selected groups do not have the required permissions, the corresponding dropdown options are disabled to prevent unauthorized actions.

You can now add custom text and supporting links directly within LM Logs alert rules.
This enhancement introduces a custom text field that enables you to include contextual information such as runbook links, knowledge base articles, escalation instructions, or system diagrams in the alert payload.

You can now save and automatically restore column configurations with your log queries. When you save a query, LogicMonitor also saves the selected column configuration from the field panel.

When you reload or share a saved query, the custom column view is automatically restored, eliminating the need to repeatedly reconfigure fields for different log types. This enhancement improves efficiency and reduces errors when switching between logs such as Apache web logs and firewall logs.

Each LogAlert Group is scoped to a single partition, with RBAC controls (Manage/View/No Access) applied at the partition level. LogAlert Group limits are now enforced per partition, enabling better management of alerts within each partition.

Each partition supports up to 20 LogAlert Groups. Each LogAlert Group supports up to 55 LogAlerts, including up to 10 window alerts and 10 stateful alerts.

Existing LogAlert Groups continue to function without disruption.

To request higher limits, contact your Customer Success Manager (CSM).
For more information, see LogAlert Groups in the product documentation.

You can now manage Uptime Checks using Terraform to enable consistent and scalable monitoring configurations.

This feature now supports creating, updating, retrieving, and deleting Uptime Checks through the LogicMonitor Terraform Provider. You can define monitoring resources as code and manage them using standard Terraform workflows to improves consistency and reduce manual setup.

For more information, see LM Uptime in the product documentation.

The enhanced vmware.vsphere.sdk snippet enables you to process vCenter inventory faster with on-demand loading and a shared one-hour cache, which reduces repeated scans. You now experience more efficient folder traversal and improved stability during cluster host expansion with null-safe handling. These updates reduce vCenter load and help minimize timeouts in large or busy environments.

For more information, see VMware vSphere Monitoring in the product documentation.

The enhanced {{lm.topo.data }}snippet has improved error handling for MAC-to-HEX conversions. You can now experience more reliable topology discovery, reducing the likelihood of parsing failures and unexpected topology failures.

The updated Cisco Meraki NetScan now improves how duplicate resources are named during discovery. When hostname.source is configured as NetScan, the system assigns a unique display name to duplicate resources. You can more easily identify resources and avoid naming collisions across discovered devices.

For more information, see Cisco Meraki Monitoring in the product documentation.

The enhanced Cisco Catalyst Center NetScan now supports the discovery of resources that do not have a Site ID configured. This improves discovery coverage in environments where resources are not yet associated with a site.

You can also control whether credentials are automatically assigned to discovered resources. The new optional property, cisco.catalyst.credentials.addToAllDevices determines credential behavior. When the property is set to false, discovered resources are created without adding credentials. The default value is true, which adds credentials to discovered resources.

For more information, see Cisco Catalyst Center in the product documentation.

You can now control how existing resources are updated during Enhanced Script NetScan execution using the new Criteria for updating Existing Resources dropdown.

This enhancement enables you to restrict updates to specific resources, such as those discovered by the current NetScan, resources in selected groups, or resources monitored by selected collectors.

To access this feature, navigate to Settings > NetScans > Add NetScan Options > Add Advanced NetScan, and locate the Criteria for updating Existing Resources dropdown in the configuration workflow.

For more information, see Enhanced Script NetScan in the product documentation.

You can now view datapoints side by side as columns in the Metric Explorer Report and the Advanced Metric Widget. This improves comparison and clarity. Each datapoint displays as an independent column for improved analysis.

For more information, see Metric Explorer Report and Advanced Metric Widget in the product documentation.

LogicMonitor has updated LogicMonitor REST API v3 Swagger, v3 Python, and v3 GO SDK files with the following new API endpoints:

The updates will be available after LogicMonitor v237 deployment to production is complete. For more information, see REST API Change Log and REST API v3 Swagger Documentation in the product documentation.

As LogicMonitor commits to modernizing the platform and ensuring improved performance, security, and long-term scalability to provide a seamless API experience, access to the API v1 and v2 will no longer be made available for new LogicMonitor accounts. If you are currently using API v1 or v2, your access will not be impacted. You may continue use without interruption.

You can now view usage reporting for Automated Diagnostics. The usage report provides improved visibility into on-demand and automated execution of diagnostic scripts across your LogicMonitor portal. The report enables you to monitor diagnostics usage against the entitled execution quota. Monthly usage is measured as the daily average of total executions run across your LogicMonitor portal. On the Usage Reporting page, you can view the count of entitled daily quota, current daily executions, and historical daily executions. By default, the execution count for the current day of the month displays.

To access this feature, navigate to Settings > Usage, and select “Automated Diagnostics” from the Product dropdown menu.

For more information, see Usage Reporting for Automated Diagnostics in the product documentation.

You can now configure Single Sign-On (SSO) settings using a dedicated permission for SSO configuration. This enhancement separates SSO management from the User Access permission and provides more precise control over authentication settings. Any existing User Access role permission is copied to the new Single Sign-On permission.

To access this feature, navigate to Settings > Single Sign-On.

For more information, see Enabling Single Sing-On in product documentation.

In a future release of LogicMonitor, access to Websites will be removed for environments that do not have access to the Websites product in Usage Reporting only. You can accomplish this same functionality using LM Uptime.

For more information about this deprecation, including timeline and further updates about the removal, see Upcoming End of Sale (EOS) for “On-Demand” Legacy Websites (LWM) in LM Community.

For the most up-to-date information about how to continuously monitor websites, servers, and networking hardware from multiple locations, see LM Uptime Overview in the product documentation.

If you have any questions or require assistance during this process, contact the Support team or your Customer Success Manager.

In a future release of LogicMonitor, support for legacy LM Container builds and Argus versions 5, 6, 7, and 8 will be discontinued. If you are running these versions, you must upgrade to a supported LM Container release to continue receiving updates and support.

The latest LM Container releases provide:

• Improved monitoring accuracy through updated and actively maintained code paths

• Latest security patches and compliance updates for modern Kubernetes environments

• Ongoing compatibility with newer Kubernetes versions and container runtimes

For more information about this

deprecation, including timeline and further updates about the removal, see Upcoming End of Life (EOL) for Legacy Versions 5, 6, 7, and 8 for Legacy LM Container & Argus in the LM Community.

If you have any questions or need assistance during the migration, contact the Support team or your Customer Success Manager.