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
- SNMP Trap MIBs
- 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
- AWS Cost by Tag Monitoring
- Active Discovery and AWS CloudWatch Metrics
- 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
- 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 Integration YAML File
- Edwin AI Custom Integrations
- 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 Cost Optimization Recommendations
- 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
- HAR File in LogicMonitor
-
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
In this article
Feature Highlights
- Launched LogicMonitor Data Publisher Service
- Launched MIBs to JSON Converter Utility
- Auto Conversion of Linux Collectors to Non-root Users during Upgrade
- Renewed LMSignCert
- SNMP Trap Translation Improvements
LogicMonitor EA Collector 35.400 is released on April 29, 2024. It is based on the previously released EA Collector 35.300 and includes the following additional updates.
If you have collectors that are active since past 6 months but are below the minimum required version MGD Collector 33.007 (released on October 6, 2023), we request you to upgrade your collectors to the MGD Collector 33.007 or a later version by May 16, 2024. Post this deadline, collectors which are below the MGD version will stop sending data to the LogicMonitor platform. Additionally, due to changes in the authentication mechanism of the platform, after May 16, such collectors will not be able to communicate with the LogicMonitor platform.
Launched LogicMonitor Data Publisher Service
We have introduced LogicMonitor Data Publisher service under the Beta program. It is an integrated service with an ability to extract and send real-time datasource metrics to a third party destination. Currently, the service supports integration with Kafka. If you want to participate in Beta and access this feature, contact your LogicMonitor CSM. For more information, see LogicMonitor Data Publisher Service in the product documentation.
Launched MIBs to JSON Converter Utility
Starting with EA Collector 35.400, you can use the MIBs to JSON Converter Utility to convert the MIB files to JSON files. In the collector, the utility is located at [LogicMonitor Collector Directory]/bin/snmpMibsToJsonConversionUtil. This Python-based utility is designed to convert the custom MIBs (which LogicMonitor does not support out-of-the-box) to enterprise JSON files, which the collector then uses to translate the SNMP traps. For more information, see Translating SNMP Traps Using Custom MIBs in the product documentation.
Auto Conversion of Linux Collectors to Non-root Users during Upgrade
When you upgrade Linux collectors to EA Collector 35.400 or later version, the Linux collectors which are currently operating under root account user are automatically migrated to non-root account user.
Renewed the LMSignCert
LogicMonitor has renewed the LMSignCert which is used to sign the Collector installer and Windows binaries.
Note: Collector will continue to function as designed and no action is expected from customers.
SNMP Trap Translation Improvements
Enterprise JSON files (converted from custom MIBs using the utility present in the [LogicMonitor Collector Directory]/bin/snmpMibsToJsonConversionUtil directory) present in /snmpdb/custom directory are used for SNMP trap translation along with the enterprise JSONs present in the /snmpdb/core directory. For the common enterprise JSON files present in both the core and custom directory, if common traps or OIDs are present in these files, the SNMP traps are translated using the JSON file present in custom directory. For exclusive traps or OIDs, the SNMP trap translation will work as per the corresponding JSON file.
Prevent Npcap Module Installation
When installing Windows collector in silent mode, you can use the parameter /np
to prevent the collector installer from installing the Npcap module.
Added Support for ojdbc11-23.3.0.23.09.jar
EA Collector 34.500 supports the oracle_jdbc-1.1.jar
by default. However, if you want to use the ojdbc11-23.3.0.23.09.jar
, go to the wrapper.conf settings and replace ../lib/oracle_jdbc-1.1.jar
with ../lib/ojdbc11-23.3.0.23.09.jar
.
Upgraded TLSv1.3
Upgraded the TLSv1.2 version to TLSv1.3 for a secure communication between collector and LogicMonitor portal. To override the default TLSv1.3 version, add the property httpapi.tls.version=TLSv1.2
to the agent.conf settings.
WinRM Improvements
To solve the scaling issues, WinRM now uses SBProxy for data collection.
Non-admin Configuration Improvements
To simplifying Windows non-admin configuration, you can now use a single script Windows_NonAdmin_Config.ps1
instead of multiple scripts.
Enhanced Field Mapping for Ingestion of Syslog as LM Logs
Facility, Severity, and Application from a Syslog are added by default through the agent.conf flow (lmlogs.syslog.enabled=true
) for log ingestion.
Enhanced Resource Mapping for Ingestion of SNMP traps and Syslog as LM Logs
When the SNMP traps and Syslog are processed for log ingestion through the agent.conf flow (lmlogs.syslog.enabled=true
and lmlogs.snmptrap.enabled=true
), the collector adds system.hostname
, system.sysname
, and system.ips
for resource mapping. If either of these properties match with a resource, the resource is mapped with the log. The keys and their corresponding values are given in the following table.
Key | Value |
system.hostname | HostName |
system.sysname | FQDN |
system.ips | IP |
Added httpapi.tls.version Property
Added a property httpapi.tls.version
to the agent.conf settings. Its default value is TLSv1.3.
Fixed an issue where after upgrading to EA Collector 35.100, script based modules with Groovy version v4 failed.
Fixed an issue where due to the missing [jsoup.jar] file during the downgrade process, the collector failed to downgrade from GD 35.000 and EA 35.200 to a previous version.
Fixed an issue where collector did not use the resource properties to authenticate SNMP traps if no LogSource was applied on the resource for ingestion of traps as LM logs. With this fix, resource properties are used for trap authentication, even if no LogSource is applied on the resource.
Fixed an issue where EventSources that have the same filter condition, capture SNMP traps event for one of EventSources and failed to capture for the other EventSources and did not receive an alert for that trap.
Fixed an issue where the Configure option of the deprecated Configure utility was displayed in the Start menu > Logicmonitor folder.