v.241 Release Notes

Cost Optimization Recommendations can now detect underutilized GCP Compute Engine virtual machines and recommend size adjustments with estimated annual savings.

This enables you to easily identify Compute Engine VMs that do not use their full computing capacity, and optimize your cloud spending by changing the VM size to match your workload.

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

In LogicMonitor Dashboards, you can now create Cloud Provider Health Event widgets. This widget displays events within your cloud environments, including details about their impact and status, directly on your LogicMonitor dashboard. This enhancement enables you to monitor cloud provider health events alongside other operational data.

You must have access to Cost Optimization tools to access Health Event widgets.

To configure a Health Event widget, navigate to Dashboards and select Add Widget > Cloud Provider Health Event

For more information, see Cloud Provider Health Events Widget in the product documentation.

You can now apply filters directly to individual Gauge widgets. This enables each widget to display a focused subset of data independent of other widgets on the same dashboard, providing greater flexibility when creating dashboard visualizations.

To access this feature, navigate to Dashboards and edit a Gauge widget configuration.

For more information, see Gauge Widget in the product documentation.

The enhanced cisco.dnac snippet now supports Cisco DNA Center dna/data API endpoints, including the networkDevices endpoint, while maintaining compatibility with the legacy network-device endpoint. You can use the networkDevices endpoint to avoid a known issue with the legacy endpoint that can prevent all devices from being returned when pagination is enabled. This endpoint is recommended for large environments.

To use the networkDevices endpoint, set cisco.dnac.use.network.devices to true.

The enhanced Rubrik Security Cloud NetScan now places discovered resources in the correct nested resource groups under the configured root folder. You can maintain improved resource organization because status or location groups, such as Connected, are no longer created at the portal root.

You can control the root folder for discovered resources with the optional property custom.folder.name. The default value is “Rubrik Security Cloud.”

For more information, see Rubrik Security Cloud Monitoring in the product documentation.

Cisco Meraki NetScan no longer checks the system.hostname and system.ips properties. Configurable options on the NetScan page now manage these settings, preventing resources from being incorrectly ignored during discovery.

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

You can now monitor server hardware through the Redfish REST API across multi-vendor environments. This package provides visibility into server health, performance, storage, power, cooling, networking, and PCIe components through supported BMC platforms.

The package supports Redfish-compliant server hardware and has been validated with Dell iDRAC, HPE iLO, and Lenovo XClarity Controller platforms.

To access this feature, navigate to the LogicMonitor Exchange and import the Redfish Server Monitoring LogicModules.

For more information, see Redfish Server Monitoring in the product documentation.

You can now assign separate Diagnostics: View, Diagnostics: Execute, Remediation: View, and Remediation: Execute permissions at the resource group level. This change simplifies permission management and provides more granular control over Diagnostics and Remediation access.

• Users with Diagnostics: Execute or Remediation: Execute permissions can run DiagnosticSources or RemediationSources and view the results.

• Users with Diagnostics: View or Remediation: View permissions can view results only.

Users with the existing Diagnostic Source or Remediation Source permissions will automatically receive the corresponding Diagnostics: Execute or Remediation: Execute permissions.

To access permissions, navigate to Settings > Users and Roles > Roles tab > Add Role. Add the required details in the Add Role wizard. At the Permissions step, select the Resources tab.

For more information, see Resources Role Permissions in the product documentation.

The paloalto.prismasdwan snippet now correctly handles HTTP 403 authentication failures. This enhancement prevents duplicate retry attempts when authentication fails, resulting in more accurate retry behavior.

In a future release, LogicMonitor Collectors will no longer support Apache Groovy 2. All official LogicMonitor-provided modules are compatible with Apache Groovy 4. To support this migration, LogicMonitor released updates to official LogicModules to be compatible with Groovy 4.

As a result of this migration, you must do the following:

• Validate any customized or community-provided modules to ensure compatibility
  For more information about validating your customized modules, see Custom Module Groovy Migration Validation in the product documentation.
• Install a module update for LogicMonitor-provided modules that have compatibility changes released.
  For more information, see LogicMonitor Provided Modules Groovy 4 Migration in the product documentation.
• Update Enhanced Script NetScans to Groovy 4 compatible scripts.
  For more information, see “Enhanced Script NetScans Now Groovy 4 Compatible” in the Modules section of the Release Notes.

For more information on the timeline of this migration, see Apache Groovy 2 End-of-Life Milestone Public Announcement.

The GD Collector 39.004 now uses Groovy 4 instead of Groovy 2.

When running a module using Apache Groovy 4, the following exception can be thrown when using the GroovyScriptHelper to incorporate LogicMonitor snippets in your script:

exception:groovy.lang.MissingPropertyException: No such property

To mitigate this issue, adjust the way the class is imported, similar to the following:

import com.santaba.agent.groovy.utils.GroovyScriptHelper 
import com.logicmonitor.mod.Snippets 
def modLoader = GroovyScriptHelper.getInstance(GroovySystem.version).getScript("Snippets", Snippets.getLoader()).withBinding(getBinding())

When running a module using Apache Groovy 4, and the module includes an invalid type parameter for a data structure, the module throws the following exception:

java.lang.RuntimeException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:

You can now filter resources by custom properties and system properties when configuring an Interface Bandwidth Report (IBR). You can also filter instances by instance properties and include property-based criteria directly in report configuration. This enables you to create more targeted reports without relying on broader resource or instance selections.

To access this feature, navigate to the IBR configuration page and define property-based filtering criteria.

For more information, see Interface Bandwidth Report in the product documentation.

When configuring an SDT for Monthly (on a specific day) frequency, you can now specify multiple days. Previously, you had to create separate SDT entries for each day. This enhancement reduces duplicate configuration and simplifies recurring downtime management.

You can now specify a common start time and end time across all selected days. You can also add or remove days without creating additional SDT entries. Existing single-day configurations continue to work as expected.

For more information, see Resource SDT in the product documentation.

As LogicMonitor continues to phase out the legacy UI, the New UI Preview switch will be removed from Resources (which includes Services), making Resources and Services 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, see Upcoming End-of-Life (EOL) for UIv3 Resources in LM Community.

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

LogicMonitor now includes a new SCIM tab on the Single Sign-On page, enabling you to automate user de-provisioning by synchronizing user lifecycle changes from your identity provider (IdP) to LogicMonitor using the System for Cross-domain Identity Management (SCIM) protocol.

LogicMonitor supports SCIM de-provisioning with identity providers that support the SCIM protocol, including Microsoft Entra ID, Okta, and OneLogin. When you enable the Enable SCIM switch, LogicMonitor automatically deactivates users whose accounts are deleted, deactivated, or no longer have access to LogicMonitor in the IdP. This synchronization helps keep user access in LogicMonitor aligned with the configuration in the IdP.

To use this feature, you must first configure Single Sign-On (SSO) and then manually configure SCIM. This setup includes:

• Completing the SSO configuration.

• Enabling SCIM in LogicMonitor to generate a SCIM token.

• Configuring SCIM user provisioning in your IdP using the SCIM token.

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

For more information, see SCIM Configuration in the product documentation.

The out-of-the-box Administrator role is now protected in newly created LogicMonitor portals. You can no longer modify or delete this role, which helps preserve access to critical administrative permissions and reduces the risk of accidental changes to default role configurations.

Existing LogicMonitor portals are not affected by this change and can continue to modify or delete the Administrator role as previously supported.

For more information, see Managing a Role in the product documentation.

LogicMonitor plans to transition synthetic monitoring capabilities from LM APM Synthetics (SYN) to our new product, Synthetics and Internet Performance Monitoring, which provides enhanced visibility, broader monitoring capabilities, and a modernized platform architecture.

LM APM Synthetics is built on a legacy Selenium-based architecture, while our new product, Synthetics and Internet Performance Monitoring, provides globally hosted monitoring, advanced waterfall analysis, filmstrips and playback for transaction troubleshooting, and expanded test coverage across browser, API, network, and internet performance monitoring workflows.

There is no immediate change required, and you can continue using LM APM Synthetics during the transition period, until it is fully deprecated.

For more information about this transition, including roadmap details and evaluation guidance, see the Upcoming End of Life for LM APM Synthetics in LM Community.

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

In a future release, LogicMonitor will discontinue support for legacy LM Container builds and Argus versions 5, 6, 7, and 8. If you are running these versions, 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