EA Collector – 29.102

Known issues in this version:

An update of the log4j Collector JAR (from 1.2.17 -> 2.13.2) is causing Cisco_IOS and Cisco_NXOS ConfigSources to fail. New versions of these ConfigSources are available that resolve this issue.
(Update: This issue is resolved in EA 29.106) LogicMonitor’s default use of SSE (Standalone Script Engine) to execute script DataSources is causing some LogicModules (notably Cisco Meraki DataSources) to fail to execute properly on this Collector version. As a workaround, you can disable SSE in the Collector’s configurations by updating the value of the groovy.script.runner setting to “agent”. See Editing the Collector Config Files for instructions on editing Collector configurations.

Enhancements/Updates

Adjusted the output text width of Collector debug information (as displayed in various locations in the UI such as Collector Debug Facility or test script), making Java exception text easier to read.
IPFIX flow records lacking required fields are now properly discarded.
VMware detection now correctly differentiates between vCenter, ESXi, and workstation.
The Collector installer now depends on `od` instead of `xxd`, which will fix issues installing the Collector on RHEL.
We’ve removed the following Java libraries from the Collector:
- Dom4j-1.6.1.jar
- Commons-ssl-1.0.jar
- Commons-httpclient-3.1.jar
We’ve updated the following JARs:
- jackson-databind 2.8.11.3 -> 2.11.0
- jetty-server 8.1.12 -> 9.4.3.0
- jetty-http 8.1.12 -> 9.4.3.0
- jetty-util 8.1.12 -> 9.4.3.0
- commons-beanutils 1.9.2 -> 1.9.4
- log4j 1.2.17 -> 2.13.2
- bcprov-jdk15on 1.60 -> 1.66
- jboss-remoting 5.0.0 -> 5.0.17
- commons-io 2.2 -> 2.6
- fastjson 1.2.57 -> 1.2.62
- commons-codec 1.1.0 -> 1.14

Fixed issue causing sbproxy to continuously restart on Windows Collectors when collecting Windows Event Logs.
Fixed issue where NetScan timeout in seconds was interpreted as milliseconds, causing unexpected timeout conditions.
Docker Collector installation now works for EA.