LogicMonitor recognized as a Customers' Choice by Gartner Peer Insights™ in 2024 Gartner Voice of the Customer for Observability platforms.

Read More

EA Collector 36.200

Last updated on 07 August, 2024

Feature Highlights

  • Static Bearer Token Authentication Enabled for HTTPS Publisher
  • New Wrapper Log Components for LogSource Flows

LogicMonitor EA Collector 36.200 is released on August 07, 2024. It is based on the EA Collector 36.100 and includes the following additional updates.

Enhancement

Static Bearer Token Authentication Enabled for HTTPS Publisher

LogicMonitor now supports static bearer token authentication for the HTTPS Publisher. You can activate the auth mode by enabling agent.publisher.enable.auth=true and pass the bearer token in the publisher.http.bearer.token=Encrypted Token property in the agent.conf settings.

Enhancement

New Wrapper Log Components for LogSource Flows

On the Collector Logs page, you can now access separate log components for SNMP Traps and Syslog as Logs. Previously, a common component eventcollector.syslog was used for both the Syslog EventSource and LogSource. LogicMonitor has now added logcollector.syslog for Syslog LogSource (also for ingestion of Syslog events as LM logs through the agent.conf settings). The existing eventcollector.syslog is used for SysLog EventSources.

Similarly, a common log component eventcollector.snmptrap was previously used for both the SNMP Trap EventSource and LogSource. LogicMonitor has now added logcollector.snmptrap for SNMP Trap LogSource (also for ingestion of SNMP traps as LM logs through the agent.conf settings). The existing eventcollector.snmptrap is used for SNMP Trap EventSource.

Additionally, for Windows, you can access separate log components eventcollector.wineventlog for EventSource and logcollector.wineventlog for LogSource.

Enhancement

SNMP Trap Message Formatted as JSON

To format the SNMP trap messages as JSON, you can set the lmlogs.snmptrap.formatMessageAsJson.enabled property to true in the agent.conf settings. Also, the translated variable binding keys of the SNMP trap are included in a single log field, instead of individual log fields for each translated variable binding key. By default, the lmlogs.snmptrap.formatMessageAsJson.enabled property is set to false.

Enhancement

Setting groovy.v4.classloader.enable to True

Windows Collector running with Groovy v4 scripts can sometimes result in JSON Slurper errors. You can fix the errors by setting groovy.v4.classloader.enable to true in the agent.conf settings. Previously, by default, it was set to false. In this release, we have changed its default value to true.

Enhancement

Support for Processing and Storing NBAR2 Data Asynchronously

For NetFlow, LogicMonitor now supports asynchronous processing and storage of NBAR2 data, thus improving the overall NetFlow collector performance. By default, the netflow.use.new.nbar.logic property is set to true in the agent.conf settings for asynchronous NBAR2 data processing.

Resolved Issue

Fixed an issue where Active Directory (AD) specific to SNMP did not function correctly for Fortinet devices due to the presence of additional octet in the IP addresses for both IPV4 and IPV6.

Resolved Issue

Fixed an issue where on the Collector Status page, for the Collector Business Metrics, the BatchScript NaN percentage was beyond 100%.