EA Collector 31.100

Last updated on 15 October, 2022

LogicMonitor EA Collector 31.100 was released on February 17, 2022 and includes the following updates and fixes.


  • Made improvements to LiveHostSet implementation of data store using chronicle map. This will reduce chronicle map corruption and ensure that script cache will remain after Collector reboot.
  • Added support for three new LogicModules: Windows Events Logs Collection, Kubernetes Events, and Kubernetes Pod Logs.
  • If you have Synthetics enabled, and you have defined variables in your SIDE file, you can now insert variable values via configuration. You can set them to an instance property, device property, or agent configuration.
  • Added debug commands to Syslog LogSource for troubleshooting issues such as pushed logs not being sent to LogicMonitor for a device after applying LogSource.
  • For Linux users, the permission assigned to the agentid.cache file is no longer dependent on the umask value set in customer environments.
  • Added the ability to select more than one label for instance definitions in the OpenMetrics wizard. You can now create a unique instance key if a single label is not sufficient.
  • Added two new fields to the Netflow Collector: ‘PACKETS_TOTAL’ (field ID = 86) and ‘BYTES_TOTAL’ (field ID = 85) . To add these fields, we added two new properties: netflow.latestFlowRecordCache.maxSize and netflow.latestFlowRecordCache.recordExpireInterval.
  • Upgraded SSHJ library from version 0.27.0 to 0.32.0. We also improved the user auth implementation for SSHJ. The new implementation now supports the “none” authentication method and the public key authentication.
  • Added a whitelist for SHA file verification to ignore unnecessary file verification checks and prevent misleading warnings in the logs. Files with .txt, .pid, and .lock are excluded from SHA verification.
  • Extended Collector support for NetFlow monitoring for Meraki devices. We also resolved an issue that prevented Meraki devices with hostnames ending with “.invalid” from resolving DNS for endpoints on the Traffic tab.
  • Added a new configuration variable to the agent.conf file ‘autoprops.detectors.ignore.snmp.versions’ to ignore SNMP v1, v2c, and v3 detection tasks by passing either v1, v2c, or v3 values. This prevents autoprop tasks for specified SNMP versions from getting blocked due to the firewall security in the customer environments.
  • The Credential Vault integration now runs successfully for PropertySources. PropertySources are now applied to the devices that have Vault integration enabled.
  • Improved settings related to log processing and removed the flags for enabling a specific LogSource implementation. Without enabling any flags in the agent.conf file, the LogSource will now start processing logs as soon as users apply LogSource to a device.
  • Batch script data collection instance mapping is no longer case sensitive.

Bug Fixes

  • Fixed an issue that prevented Collectors from upgrading from GD Collector 30.000 to EA Collector 30.102.
  • Fixed an issue that prevented Collectors from upgrading because the previous upgrade package failed to exit. The timeout of the upgrade process is now configurable using the configuration variable “upgrader.exit.wait.time.Insec” and defaults to 30 seconds.
  • Fixed an issue where LM Logs used the property  lmlogs.syslog.useTimestampWhenCollectorReceivedLogs=true from the agent.conf file even if the Use Received Time instead of Log Timestamp setting was set to “false”.
  • Fixed an issue where a Collector incurred exceptions in the logs as the script parameters were not getting parsed for external PowerShell scripts such as wmi.pass and wmi.user without quotes on the DataSource configuration page.
  • Fixed an issue that prevented the Bootstrap installer from downloading for Linux Collectors.
  • Fixed an issue where, while installing a Collector using a proxy, if the proxy.port value is not provided on the command line, the proxy.port value is displayed the same as the proxy.host value in the agent.conf file after installation.
  • Fixed issues with CWE-757 and CWE-297 in SNISSLSocketFactory in Collectors.
  • Fixed an issue where MongoDB instances were not discovered during Active Discovery using the Mongo Discovery task.
  • Fixed an issue where after a Collector was downgraded from version 31.100 to 30.001, the proxy details were not retained in the website.conf file.
  • Fixed an issue that led to an error when installing a Collector using Kubernetes.
  • Fixed an issue where the elapsed time was calculated incorrectly when the PropertySource task failed.
  • Fixed the Windows Collector installation issue where the installer failed to accept proxy details entered in the Proxy settings.
  • Fixed an issue where the OpenMetrics collection task for multi-instance DataSources failed to get the Active Discovery result.
  • Fixed an issue where the Windows Event Log alert messages displayed garbled Japanese 2 byte characters.
  • Fixed an issue with the Windows Collector which prevented some OpenMetrics from being reported to Santaba.
  • Fixed an issue where Active Discovery failed to parse due to an empty instance in the discovered instances from OpenMetrics.
  • Fixed a parsing issue in NetFlow that occurred due to no value in the OUT_PKTS/OUT_BYTES fields in a Collector. The value of IN_PKTS/IN_BYTES will now be populated in these fields.
  • Fixed an issue that led to failure in getting Batch script output results in a Windows Collector due to the new line character “/r/n”. System.lineSeparator now splits new lines in Batch script output for all OS types.
In This Article