Release Note


-
LogicMonitor Platform
- Introduction to LogicMonitor
- In-App Resources
-
Account Information
- Portal Information
- Portal Settings
- Financial
-
Usage Reporting
- Usage Reporting Overview
-
Product-Specific Usage Reporting
- Usage Reporting for APM Metrics
- Usage Reporting for LM Logs
- Usage Reporting for SaaS Monitoring
- Usage Reporting for IaaS Monitoring
- Usage Reporting for PaaS Monitoring
- Usage Reporting for APM Traces
- Usage Reporting for APM Synthetics
- Usage Reporting for Devices
- Usage Reporting for Websites
- Usage Reporting for Wireless Access Points
- Audit Logs
- Ops Notes
- Security Settings
- User Access
- Collectors
-
Dashboards
- Dashboards Overview
- Dashboard Creation
- Modern Dashboards
- Adding Dashboard Groups
- Finding Dashboards and Dashboard Groups
-
Widgets
- Widgets Overview
- Widgets Creation
- Widget Datapoint Configurations
-
Widget Types
- Alert List Widget
- Big Number Widget
- Netflow Widget
- NOC Widget
- Log Query Widget
- Pie Chart Widget
- Table Widget
- Text Widget
- Website Status Widget
- Custom Graph Widget
- SLA Widget
- Topology Map Widget
- Gauge Widget
- HTML Widget
- Job Monitor Widget
- Map Widget
- Resource Explorer Widget
- Recommendations Widget
- Billing Widget
- Widget Management
- Standard Widget Configurations
- Enabling Dashboard Text Widget Script Security
- Dashboard Management
- Dashboard Distribution
-
Resource Tree
- Navigating the Resources Page
- Changing the Time Range
- Remote Session
- Using Ops Notes
- Resources Details
- Resource Groups
- Resource Management
- NetScans
- Resource Explorer
- Services
- LM Uptime Overview
-
Websites
- Data Monitored for Websites
- Websites Page Overview
- Alerting on Websites Data
- Trace Route for Websites
-
Websites Management
- Websites Default Settings
- Web Check
- Ping Check
- Testing the Steps of a Web Check
- Creating a Website Dashboard
- Website Properties
- Website Management
- Executing Internal Web Checks using Groovy Scripts
- Web Checks with Form-Based Authentication
- Websites SDT
- Disabling External Website Testing Location Across your Account
- Understanding Website Status Codes
- Websites Groups
- Mappings
- Alerts
-
Reports
- Choosing a Report Type
- Creating a Report Group
- Shared Report Access
-
Report Types
- Alert Forecast Report
- Alert SLA Report
- Alert HealthCheck Report
- Alert Thresholds Report
- Alert Trends Report
- Alerts Report
- Audit Log Report
- Dashboard Report
- Interface Bandwidth Report
- Log Query Report
- NetFlow Resource Metric Report
- Resource Group Inventory Report
- Resource Inventory Report
- Resource Metric Trends Report
- Role Report
- SDT Inventory Report
- Server CPU Report
- Service Level Agreement Report
- User Report
- Website Overview Report
-
Modules
- Modules Overview
- Modules Installation
- Custom Module Creation
- Tokens Available in LogicModule Alert Messages
- Deprecated LogicModules
- Data Collection Methods
- Active Discovery
- Groovy Support
-
Module Configurations
- Types of Modules
- DataSource
- PropertySource
- AppliesTo
- SNMP SysOID Map Configuration
- JobMonitor
- ConfigSource
- TopologySource
- EventSource
-
LogSource
- LogSource Overview
- Configuring a LogSource
- Kubernetes Event Logging LogSource Configuration
- Kubernetes Pods LogSource Configuration
- Log Files LogSource Configuration
- Script Logs LogSource Configuration
- SNMP Traps LogSource Configuration
- Supported MIBs for SNMP Trap Translation
- Troubleshooting MIBs to JSON Converter Utility Issues
- Troubleshooting SNMP Traps Issues
- Modules Management
- Access Groups for Modules
- Security
-
LM Logs
- LM Logs Overview
- Log Ingestion
- Log Processing
- Logs Partition
- Log Anomaly Detection
- Log Analysis
- Viewing Logs and Log Anomalies
- Reset Log Anomaly Detection
- Log Patterns
- Log Query Language
- Log Processing Pipelines
- Log Alert Conditions
- Logs Roles and Permissions
- LM Logs Usage Data
- Troubleshooting Logs
-
Cloud Monitoring
- Introduction to Cloud Monitoring
- Cloud Services and Resource Units
- Monitored Locations for Cloud Monitoring
- Cloud Monitoring using a Collector for Existing Cloud Resources
- Monitoring Utilized Cloud Service Limits
- Custom Event Integrations Setup
-
Amazon Web Services Monitoring
- AWS Monitoring Setup
- AWS Organizational Unit Monitoring Setup
- Using StackSets to Automate Role and Policy Creation
- AWS Billing Monitoring Setup
- CloudWatch Costs Associated with Monitoring
- Managing your AWS devices in LogicMonitor
- AWS Tag Usage in LogicMonitor
- Customizing AWS CloudWatch DataSources
- Troubleshooting Custom AWS CloudWatch DataSources
- Microsoft Azure Monitoring
- Google Cloud Platform Monitoring
- MongoDB Atlas Monitoring
- Cost Optimization
- Cloud Data Collection with Poll Now
- SaaS Monitoring
-
Edwin AI
- Introduction to Edwin AI
- Key Concepts in Edwin AI
- Edwin AI Roles and Users
- Configure Edwin AI Dashboard
- Configure Edwin AI Models
- Configure Edwin AI Actions
- Edwin AI Rules
- Working with Edwin AI
- Export and Import Edwin AI Configuration
-
Edwin AI Integrations
- Edwin AI Integrations Overview
- Edwin AI Monitoring Integrations
- Edwin AI IT Service Management Integrations
-
LM Integrations
- LogicMonitor Integrations Overview
- Navigating the Integration Page
- Communications Integrations
- Workflow Integrations
- Automation Integrations
- Custom Integrations for LogicMonitor
- Logs for LM Integrations
-
Container Monitoring
- About LogicMonitor Container Monitoring
-
Kubernetes Monitoring
- Support Matrix for Kubernetes Monitoring
- Kubernetes and LM Containers Key Concepts and Terms
- Kubernetes Monitoring Considerations and Required Permissions
- Resource Sizing for Performance Optimization and Tuning Recommendations
- LM Container Installation
- LM Container Upgrade
- LM Container Uninstallation
- Existing Configuration Migration
- Kubernetes Events and Pod Logs Collection
-
Resource Monitoring
- Monitoring Helm Charts Releases
- Kubernetes Core Components Monitoring
- Monitoring Kubernetes Clusters with kube-state-metrics
- Filtering Kubernetes Resources for Monitoring
- NGINX Ingress Controller Monitoring
- Kubernetes Certificates and cert-manager Monitoring
- Disabling Alerts on Kubernetes Resources
- Default Filtering for Kubernetes Resources
- Filtering Kubernetes Resources using Labels, Annotations, and Selectors
- Disabling Resources from Monitoring
- Retention of Deleted Kubernetes Resources using LM Containers
- Retaining Deleted Kubernetes Resources
- Advanced Configuration
- Monitor Supported Resources
- Topology for Kubernetes Cluster
- Kubernetes Cluster Monitoring as Non-Admin User
- Troubleshooting Kubernetes Monitoring
- Docker Monitoring
-
LM APM
- LM APM Overview
- Quick Steps to Setup LogicMonitor APM
-
Push Metrics
- Getting Started with Push Metrics
- Use Cases for Push Metrics
- About the Push Metrics REST API
- Ingesting Metrics with the Push Metrics REST API
- Python SDK for Push Metrics API
- .NET SDK for Push Metrics API
- Managing Resources that Ingest Push Metrics
- Rate Limiting for Push Metrics
- Updating Instance Properties with the Push Metrics REST API
- Updating Resource Properties with the Push Metrics REST API
- OpenMetrics Integration
-
Distributed Tracing
- Distributed Tracing Overview
- Application Authentication Overview
- Traces Page
- Application Instrumentation for LogicMonitor
- Trace Data Forwarding to LogicMonitor
- OpenTelemetry Collector for LogicMonitor Overview
- Synthetics
-
Monitoring Solutions
- Apache
- APC
- AI Monitoring
- Atlassian
- AWS
- Azure
- Broadcom
- Cato Networks
- Checkpoint
-
Cisco
- Cisco APIC Monitoring
- Cisco ASA/ASR
- Cisco Catalyst Center
- Cisco Catalyst SD-WAN Monitoring
- Cisco CUCM API Monitoring
- Cisco Device SNMP and NTP Configuration
- Cisco Firepower Chassis Manager Monitoring
- Cisco Firepower Threat Defense Monitoring
- Cisco Hyperflex Monitoring
- Cisco Intersight Monitoring
- Cisco IP SLA Monitoring
- Cisco ISE Monitoring
- Cisco Meraki Monitoring
- Cisco UCCX Monitoring
- Cisco UCS Monitoring
- Cisco UCS X Monitoring
- Cisco Unified Call Manager (CUCM) Monitoring
- Cisco VoIP Monitoring
- Cisco Wireless Monitoring
- Citrix
- Cohesity
- Common Config
- CommVault
- ConnectWise
- Couchbase Server
- Dell Technologies
- Email Service
- Extreme Networks
- F5
- FreeBSD
- Fortinet
- HPE
- IBM
- IMPI
- Infinidat
- Infoblox
- Java
- Jenkins
- Juniper
- Kemp
- Kubernetes
- Linux
- LogicMonitor
- LSI MegaRAID Controller
- Microsoft
- MongoDB
- NetApp
- Network Traffic Monitoring
- NTP
- Nutanix Systems
- OpenAI
- Oracle
- Palo Alto Networks
- Panzura
- Perfmon Access
- Pick
- Puppet
- Pure Storage
- Quantum
- RabbitMQ
- Redis
- Rubrik
- Ruckus
- SAP
- Slack
- SSL
- SNMP
- Sonicwall
- SumoLogic
- SwiftStack
- Ubiquiti
- Unomaly
- Varnish
- Veeam
- Versa SD-WAN
- Mobile
-
Developer
-
LogicMonitor REST API
-
REST API Overview
- Using LogicMonitor's REST API
- Migration to LogicMonitor REST API v3
- REST API Change Log
- REST API Authentication
- REST API Status Codes
- REST API Error Codes
- REST API Rate Limit
- REST API Troubleshooting
-
REST API v3
- REST API v3 Swagger Documentation
- LogicMonitor v3 SDK
- REST API Basic Filters
- REST API Advanced Filters
- Creating Services Using LogicMonitor REST API v3
- Delta Support for device/devices API
- Best Practices for Migrating to LogicMonitor v3 SDK
-
REST API v3 Endpoints
- Managing Alerts
- Managing Alert Rules
- Managing Recipient Groups
- Managing Roles
- Managing Ops Notes
- Managing Report Groups
- Managing Dashboard Groups
- Managing Collector Groups
- Managing ConfigSources
- Managing EventSources
- Managing Collector Debug Command
- Managing Collector Version
- Managing NetScan
- Managing PropertySources
- Viewing Metrics
- Viewing Integration Audit Logs
- Viewing External APIs
- Managing AppliesToFunction
- Managing Devices
- Managing DataSources
- Managing Escalation Chains
- Managing API Tokens
- Managing DataSource Instances
- Managing Dashboards
- Managing Users
- Managing Audit Logs
- Managing Data
- Managing Access Group
- Managing OIDs
- Managing Device Groups
- REST API v2
-
REST API v1
- REST API v1 Overview
- Getting Data with the REST API
-
REST API v1 Endpoints
- Managing Alert Rules
- Managing Alerts
- Managing API Tokens
- Accessing Audit Logs
- Managing Collectors
- Managing Collector Groups
- Managing Dashboards and Widgets
- Managing Dashboard Groups
- Managing DataSources
- Managing DataSource Instances
- Managing Devices
-
Managing Device Groups
- About the Device Group Resource
- Add a Device Group
- Add Device Group Properties
- AWS Device Groups
- Azure Device Groups
- Delete Device Group Properties
- Delete a Device Group
- GCP Device Groups
- Get all alerts for a Device Group
- Get all SDTs for a Device Group
- Get Device Group Properties
- Get Device Groups
- Get devices for a particular device group
- Update a Device Group
- Update Device Group Properties
- Managing Escalation Chains
- Managing Ops Notes
- Managing Reports
- Managing Report Groups
- Managing Roles
- Managing SDTs
- Managing Websites
- Managing Website Groups
- Getting Websites Test Locations
- Managing Thresholds
- Managing Users
-
REST API Overview
- Scripting Support
-
LogicMonitor REST API
- Policies and Compliance
- Training and Education
-
Legacy UI
- Getting Started
- Devices
- Dashboards and Widgets
- AIOps
- LM Service Insights
- LogicModules
- Terminology and Syntax
- LM APM
-
Cloud Monitoring
-
Getting Started with LM Cloud
- LM Cloud Monitoring Overview
- Enabling Cloud Monitoring using Local Collector
- Visualizing your cloud environment with auto dashboards and reports
- Setting up custom event integrations
- Monitoring Cloud Service Limit Utilization
- Optimizing your Cloud Spend
- Cloud Data Collection
- Amazon Web Services Monitoring
- Google Cloud Platform Monitoring
- MongoDB Atlas Monitoring
-
Getting Started with LM Cloud
- Container Monitoring
- Monitoring Solutions
Feature Highlights
- Resource Explorer Widget Now Available
- Cost Optimization Now Supports FOCUS 1.0 Schema for Azure
- Improved Cisco Meraki Monitoring NetScan
Monitoring Updates
- Updated the Cato SDWAN Interfaces and Tunnels modules ActiveDiscovery
- Updated graph datapoint in Microsoft_Azure_ActiveDirectoryApplicationSecrets
- Updated Cisco_Transceiver_Sensors module
Alerts
Enhanced Config Alerts Overview Details
The Config Alerts Overview now provides detailed information about alerts generated for specific ConfigSource versions.
This enhancement offers greater visibility into configuration-related issues and their impact on your environment.
For more information, see Viewing Config Checks in our product documentation
Cost Optimization
Cost Optimization Now Supports FOCUS 1.0 Schema for Azure
Billing monitoring in Cost Optimization now supports the FOCUS 1.0 cost and usage schema for Azure exports.
Dashboards
Resource Explorer Widget Now Available
A new widget tracking Resource Explorer data is now available in the LogicMonitor dashboard. Create new custom views or load from saved Resource Explorer views for quick access to summarize resource health. For more information, see Resource Explorer Widget
Note that resource explorer widgets do not support sharing via embedded URL. For more information on configuring Resource Explorer views, see Resource Explorer. For more information on configuring widgets, see Widget Creation.
Modules
Improved Cisco Meraki Monitoring NetScan
The updated Enhanced Script NetScan for Cisco Meraki now uses the new recommended Meraki endpoint for retrieving data, replacing the previously deprecated endpoint.
For more information, see Cisco Meraki Monitoring in the product documentation.
Apache Groovy 4 Support for all LogicMonitor-Provided LogicModules
In a future release, LogicMonitor Collectors will no longer support Apache Groovy 2. All official LogicMonitor-provided modules will be compatible with Apache Groovy 4. To support this migration, LogicMonitor will be releasing 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. The released updated modules are listed in the LogicModules Release section.
For more information, see LogicMonitor Provided Modules Groovy 4 Migration in the product documentation.
For more information on the timeline of this migration, see Apache Groovy 2 End-of-Life Milestone Public Announcement.
The LogicMonitor EA Collector 34.500 or later is compatible with Groovy 2 and Groovy 4. For more information about the EA Collector release, see the EA Collector 34.500 Release Notes.
When running a module using Apache Groovy 4, and using java.util.Date.format(), the following exception is thrown:
exception:groovy.lang.MissingMethodException: No signature of method: java.util.Date.format() is applicable for argument types: (String) values: [yyyy-MM-dd’T’HH:mm:ss z]
Note: This issue is fixed with the LogicMonitor Collector version 35.400 or later. To mitigate this issue when running a module using Apache Groovy 4, ensure you upgrade to the LogicMonitor Collector version 35.400 or later
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 runtime exception:
java.lang.RuntimeException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
Important: LogicMonitor is releasing updates to LogicModules to mitigate this issue for official LogicMonitor-provided modules. If you are leveraging customized or community-provided modules, you must update the module to pass valid parameters into all data structures.
When running a module using Apache Groovy 4 with legacy classes in your script, the following exception can be thrown:
java.lang.RuntimeException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed
To mitigate this issue, migrate to JPMS-compliant package names. Making this change does not break backward compatibility with Groovy 2.
For example, the following script uses legacy classes:
import groovy.util.XmlSlurper
import groovy.util.XmlParser
def xmlSlurper = new XmlSlurper()
def xmlParser = new XmlParser()
You can replace the legacy classes with JPMS-compliant package names in Groovy 4 to resolve the exception, similar to the following:
import groovy.xml.XmlSlurper
import groovy.xml.XmlParser
def xmlSlurper = new XmlSlurper()
def xmlParser = new XmlParser()
Important: LogicMonitor is releasing updates to LogicModules to mitigate this issue for official LogicMonitor-provided modules. If you are leveraging customized or community-provided modules, you must update the module to pass valid parameters into all data structures.
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:
if(GroovySystem.version.startsWith(“2.”)) {
modLoader = com.logicmonitor.common.sse.utils.GroovyScriptHelper.getInstance()._getScript(“Snippets”, Snippets.getLoader())
} else {
modLoader = com.santaba.agent.groovy.utils.GroovyScriptHelper.getInstance(“v4”).getScript(“Snippets”, Snippets.getLoader())
}
For example, the following demonstrates how GroovyScriptHelper is used in Groovy 2:
import com.logicmonitor.common.sse.utils.GroovyScriptHelper as GSH
import com.logicmonitor.mod.Snippets
modLoader = GSH.getInstance()._getScript(“Snippets”, Snippets.getLoader()).withBinding(getBinding())
lmDebug = modLoader.load(“lm.debug”, “0”, true)
lmDebug.default_context = “Test:SettingContext”
You can modify the script to use the GroovyScriptHelper in Groovy 4, demonstrated in the following:
import com.logicmonitor.mod.Snippets
if(GroovySystem.version.startsWith(“2.”)) {
modLoader = com.logicmonitor.common.sse.utils.GroovyScriptHelper.getInstance()._getScript(“Snippets”, Snippets.getLoader())
} else {
modLoader = com.santaba.agent.groovy.utils.GroovyScriptHelper.getInstance(“v4”).getScript(“Snippets”, Snippets.getLoader())
}
lmDebug = modLoader.load(“lm.debug”, “0”, true)
lmDebug.default_context = “Test:SettingContext”
Important: LogicMonitor is releasing updates to official LogicModules to mitigate this issue for LogicMonitor-provided modules. If you are leveraging customized or community-provided modules, you must update the module to pass valid parameters into all data structures.
Security Settings
Alert Rules Soft Limits
LogicMonitor has set a soft limit of 25% usage on the Alert Rules. For more information, see Limits, Quotas, and Constraints.
Container Monitoring Release
The following Container Monitoring releases are available:
- Container Monitoring 8.2.0 was released on September 11, 2024. For more information on new Container Monitoring features, enhancements, fixed and known issues, and the upgrade steps, see the Container Monitoring 8.2.0 Release Notes.
LogicModule Releases
New and updated LogicModules are available for you directly in your LogicMonitor portal. You can install new modules from the Exchange and update existing modules in My Module Toolbox. For more information, see Modules Installation, and Modules Management in the product documentation.
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 in the General Updates section.
Updated LogicModules
LogicModule Name | Details |
2 DataSources: – Cato_SDWAN_Interfaces – Cato_SDWAN_Tunnels | Updated the Cato SDWAN Interfaces and Tunnels modules ActiveDiscovery so that it automatically deletes instances but retains their data for 30 days, and discovers changes to instances on a 15 minute interval. |
1 DataSources: – Microsoft_Azure_ActiveDirectoryApplicationSecrets | Updated graph datapoint in Microsoft_Azure_ActiveDirectoryApplicationSecrets datasource from UntilExpiration to daysUntilExpiration. |
1 DataSources: – Cisco_Meraki_OrgDeviceCount | Added required bits and bobs snippet. |
2 DataSources: – CDP_Neighbors – SNMP_Network_Interfaces 1 TopologySources: – Networking_L2_snmpSwitch | Use IF-MIB interface name rather than CDP interface name for devices which do not return CDP interface name, like Nexus switches. |
1 DataSources: – Aruba_ClearPass_NetworkTraffic | Aggregated 4 radius values to achieve a more accurate measurement for the datapoint radiusTraffic |
1 PropertySources: – addCategory_Cato_SDWAN | Uses try/catch to get errors on bad serial numbers. Added a property for cato.sdwan.device.error as a mini-troubleshooter. |
1 DataSources: – Cisco_Transceiver_Sensors | Updated Cisco_Transceiver_Sensors module so that it’s REGEX filters include modules that start with “Twe”. This expands the set of valid discoverable instances. |
2 DataSources: – Cisco_Meraki_API – Cisco_Meraki_SwitchInterfaces 1 PropertySources: – addCategory_Cisco_Meraki_Device 1 LogSources: – Meraki Security Appliance Events | Replaces use of Cisco-deprecated getOrganizationDevicesStatuses endpoint with recommended replacements. |
1 DataSources: – VMware_ESXi_CPU | Refactored to utilize the new VMware Snippets. |