Early Release Collector - 20.074 | LogicMonitor

Product Documentation

About LogicMonitor
- Overview
- Technical Support
  - Support Overview
  - Accessing Support Resources
Getting Started
- Implementation Readiness
  - LogicMonitor Implementation Readiness Recommendations for Enterprise Customers
  - Top Dependencies for LogicMonitor Enterprise Implementation
- LogicMonitor Tutorial
- Advanced LogicMonitor Setup
LogicMonitor Concepts
- Limits, Quotas, and Constraints
Collectors
- Collector Overview
- Collector Installation
- Collector Configurations
- Collector Management
- Collector Integrations
- Collector Troubleshooting
Devices
- Adding and Managing Devices
- Device Groups
- Resources Page Overview
- Device DataSources and Instances
- Netscans
Dashboards and Widgets
- Managing Dashboards
- Managing Widgets
- Widget Types
Alerts
- About Alerts
- Alert Discovery
- Responding to Alerts
AIOps
- Anomaly Detection
  - Anomaly Detection Visualization
- Forecasting
  - Data Forecasting
- Topology Mapping
- AIOps for Alerting
LM Service Insight
- About LM™ Service Insight
- Adding Services
- Managing Services
LogicModules
- LogicModule Overview
- LM Exchange
  - LM Exchange
- DataSources
- Data Collection Methods
- Datapoints
- Active Discovery
- Groovy Support
- Powershell Support
  - Creating PowerShell Script Datasources
  - Using PowerShell Scripts in LogicMonitor
- ConfigSources
- EventSources
- Property Sources
  - Creating PropertySources
- TopologySources
  - TopologySource Overview
  - TopologySources Scripts
- AppliesTo
  - AppliesTo Scripting Overview
  - User-Defined AppliesTo Functions
- JobMonitors
- SNMP sysOID Maps
Reports
- Which report should I use?
- Creating & Managing Reports
- Scheduling a Report for Auto-Delivery
- Creating a Report Group
- Report Types
Security
- Two-Factor Authentication
- Single Sign On
- Multi Sign-On
- Configuring the Azure Active Directory SSO Integration
- LogicMonitor Security Best Practices
- Log4j Security Vulnerabilities
Settings
- About the Account Information Page
- About Audit Logs
- Message Templates
  - Alert Messages
  - New User Message
- Users and roles
Terminology and Syntax
- Scripting Support
LM Logs
- LM Logs Overview
- Log Ingestion
- Logs Query Language
- Reviewing Logs and Log Anomalies
- Log Processing Pipelines
- Log Alert Conditions
- LM Logs Roles and Permissions
- LM Logs Usage Monitoring
- Troubleshooting Logs
LM APM
- LM APM Overview
- Push Metrics
- OpenMetrics Integration
  - OpenMetrics DataSource Wizard
  - OpenMetrics Monitoring
- Distributed Tracing
- Synthetics
Cloud Monitoring
- Getting Started
- Amazon Web Services
- Microsoft Azure
- Google Cloud Platform (GCP)
SaaS Monitoring
- Airbrake Monitoring
- Microsoft Office 365 Monitoring
- SaaS Lite Monitoring
- Salesforce Monitoring
- Zoom Monitoring
Container Monitoring
- Kubernetes
- Docker
  - Docker Monitoring
Website Monitoring
- About Websites
- Adding and Managing Websites
- Website Groups
  - Adding Website Groups
  - Editing and Deleting Website Groups
Monitoring Solutions
- Applications and Databases
- Backup and Recovery Systems
- Networking and Firewalls
- Operating Systems and Virtualization
- Server and operations Hardware
- Storage Systems
- Network Traffic Flow
Workflow Integrations
- ServiceNow
  - LogicMonitor ServiceNow CMDB Integration
    - Getting Started with the LogicMonitor ServiceNow CMDB Integration
    - ServiceNow CMDB Update Set: Auto-Balanced Collector Groups
  - Service Graph Connector for LogicMonitor
    - Getting Started with the Service Graph Connector for LogicMonitor Application
- Ansible Integration
- StackStorm
- Terraform Integration
- Microsoft Teams
  - Microsoft Teams Integration Overview
  - Microsoft Teams Integration Setup
Alert Integrations
- Alert Integrations Overview
- Autotask Integration
- Campfire Integration
- ConnectWise Integration
- Custom Email Delivery
- Custom HTTP Delivery
- Integrations Logs
- PagerDuty Integration
- Puppet 4 Integration
- Puppet Integration
- ServiceNow (Incident Management) Integration
- Slack Integration
- Zendesk Integration
Mobile
- About LogicMonitor’s Mobile View and Application
- Responding to Alerts from a Mobile Device
- Viewing Alerts from a Mobile Device
- Viewing Dashboards from a Mobile Device
- Viewing Graphs from a Mobile Device
REST API Developers Guide
- Rest API Overview
- REST API v2
  - About REST API v2
  - Creating Services via the API
- Rest API v1
RPC API - Deprecated
- About LogicMonitor’s RPC API (Deprecated)
Training and Certification
- LogicMonitor Certified Professional Exam Information
- LogicMonitor Training and Certification

Early Release Collector 20.074 will be available the week of January 18, 2016. The following new features and fixes are included in this collector version:

New Features

A new BatchScript collection method is available for Datasources. Our existing Datasource Script collection method polls data per discovered instance. The new BatchScript collection method allows your collector to poll data for multiple instances at once, which is useful for script datasources that are collecting data across a large number of instances.
SNMP v3 data collection now supports the contextName and contextEngineId fields, which are used to distinguish multiple SNMP applications within the same SNMP engine.
Eventsource collection can now happen via script, eliminating the need for IPMI collection methods. This is available for testing with this collector, IPMI will be deprecated in future versions.

Upgrades

The Collector’s JRE has been upgraded to JDK 8. This addresses the security issue identified in CVE-2014-6593 and supports the GCM cipher suite. Please see this page for the operating systems and configurations officially supported for JRE8.
The MySQL JAR has been upgraded to version 5.1.38.
The Joda Time JAR has been upgraded to version 2.9.1

Bug Fixes

sFlow ports were previously being reported incorrectly in some cases.
Fixed an issue with SNMP v3 data collection related to task timeouts.
The previous EA collector auto-applied collector datasources based on device IP. This resulted in collector datasources being incorrectly applied in situations where an IP was associated with multiple devices. Collector datasources are now only applied if all IP addresses match.
TCP data collection tasks no longer fail when ‘Connection reset’ is encountered.

In This Article