v.243 Release Notes

Cost Optimization tools are now available as Cloud Operations in LogicMonitor. Cloud Operations provides a centralized location to manage cloud resource monitoring and billing. You can access cloud recommendations, provider billing, Cloud Provider Health, and Cloud Settings from a single location.

You must subscribe to the Recommendations and Billing products to access Cloud Recommendations and Billing. Cloud Settings and Cloud Provider Health are available to all LogicMonitor users.

To access this feature, navigate to Cloud Operations in LogicMonitor and select the feature you want to use.

You can now view cloud provider health events directly from Cloud Operations in LogicMonitor. This new feature displays events such as outages or other issues within your cloud environments, including details about their impact and status, enabling you to monitor health events from a central location.

To access this feature, navigate to Cloud Operations > Provider Health.

For more information, see Cloud Operations Provider Health in product documentation.

You can now use the Cloud Settings homepage as a central location to view the Cloud Accounts that are covered by your billing and monitoring configurations in LogicMonitor.

Cloud Settings enables you to view the monitoring status of your cloud environments and configure resource monitoring and billing data. From Cloud Settings, you can navigate to Resource Explorer, Cloud Recommendations, and Billing pages to view specific details. Existing resource monitoring and billing configurations are automatically displayed, and you can create new configurations directly from the Cloud Settings homepage.

For more information, see Cloud Operations Settings in product documentation.

Dashboard reports containing the Billing Forecast widget display data discrepancies across multiple forecast methods.

You can now reference ticket identifiers created by named integrations using the ##EXTERNALTICKETID.<Integration_Name>## token. This new token enables you to reuse external ticket IDs across integrations within the same alert session. For example, you can reference a ServiceNow incident ID created by one integration when triggering a Microsoft Teams integration.

To access this feature, navigate to your integration configuration and reference the ##EXTERNALTICKETID.<Integration_Name>## token in supported integration fields.

For more information, see Tokens Available in LogicModule Alert Messages in product documentation.

The enhanced veeam.vbr snippet provides improved error handling and clearer messaging when the Veeam Backup & Replication REST API user has read-only or restricted permissions.

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

The enhanced NetScan now prevents existing resources from being missed during in-script deduplication when a resource sysname contains uppercase characters.

For more information, see PaloAlto Prisma SD-WAN Monitoring in the product documentation.

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, and the module includes an invalid type parameter for a data structure, the module throws the following exception:

In Apache Groovy 4, the behavior of the push() method for the List class is reversed. In Apache Groovy 2.4, the push() method would add an item to the list, in Apache Groovy 4 push() will work on the first item of a List.

// v4 Behavior
def numbers = [1, 2, 3, 4]
numbers.push(5)
println numbers
// OUTPUT: [5, 1, 2, 3, 4]

// v2.4 Behavior
def numbers = [1, 2, 3, 4]
numbers.push(5)
println numbers
// OUTPUT: [1, 2, 3, 4, 5]

To mitigate this issue, migrate to using add() in place of push():
def numbers = [1, 2, 3, 4]
numbers.add("5")
println numbers
// OUTPUT: [1, 2, 3, 4, 5]

When running a module using Apache Groovy 4, the behavior of the pop() method is reversed. In Apache Groovy 2.4 the pop() behavior would remove the last item in a list, in Groovy 4 pop() will remove the first item in a list.

// v4 Behavior
def numbers = [1, 2, 3, 4]
println numbers.pop()
// OUTPUT: 1

// v2.4 Behavior
def numbers = [1, 2, 3, 4]
println numbers.pop()
// OUTPUT: 4

To mitigate this issue, migrate to using remove() in place of pop():
def numbers = [1, 2, 3, 4]
println numbers.remove(numbers.size() - 1)
// OUTPUT: 4

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