MGD Collector 30.002

LogicMonitor MGD Collector 30.002 was released on December 17, 2021 and includes the following bug fix:

Updated log4j to version 2.16 to mitigate the Log4shell vulnerabilities. For more information, see Log4j Security Vulnerabilities.

GD Collector 31.001

LogicMonitor GD Collector 31.001 was released on December 16, 2021 and includes the following bug fix:

Updated log4j to version 2.16 to mitigate the Log4shell vulnerabilities. For more information, see Log4j Security Vulnerabilities.

GD Collector 31.000

LogicMonitor GD Collector 31.000 was released on November 26, 2021 and includes all features and fixes from the EA Collector 30.xxx versions and more.

Enhancements

• Updated Java to Amazon Corretto 11.0.13.8.

Bug Fixes

• Fixed an issue where the OpenMetrics wizard was unable to load for Windows Collectors.
• Fixed an issue where the Linux Collector installer set the proxy.port incorrectly.
• Fixed an issue where testing the script failed for EventSources.
• Fixed an issue with NetFlow egress traffic display.

EA Collector – 30.104

LogicMonitor EA Collector 30.104 was released on October 19, 2021 and includes the following updates and fixes.

Enhancements

• Certified the Collector to run on RHEL OpenShift.
• Syslog collection for LM Logs now supports TCP.
• Linux Collector uninstaller now cleans up logicmonitor-collector-jre.conf.
• Added MongoDB 4.1.0 driver.
• Increased out-of-the-box NetFlow performance.
• Collector now loads custom JDBC JARs at boot, which lets you use other database drivers with the JDBC AD and Collection mechanisms. Add the following settings to agent.conf: custom.jdbc.drivers = com.cloudera.XXX, com.SAP.XXX . See instructions at Adding Groovy Libraries.
• The Collector installer is now signed with SHA-256 instead of SHA-1.
• LogicMonitor-created executables that ship with the Collector are now digitally signed.
• The Collector Feed is now verified by SHA-2 instead of MD5.
• Users can retrieve SHA signatures of Collector files for AV exclusion using the !DecryptFileSHA debug command.
• Increased the default threadcount for Batchscript LogicModules for XL and XXL Collectors.
• Added performance enhancements to the OpenMetrics Collector.
• NetScan now includes .0 and .255 when scanning CIDR ranges.
• PowerShell scripts are no longer written to disk before execution.
• Removed the following Perl scripts and replaced their function with corresponding Shell scripts of the same name. These shell scripts already existed on the Collector:
  • register.pl
  • sbshutdown.pl
  • uninstall.pl
  • lmbatchjobwrapper.pl
  • proxyshutdown.pl
  • configure.pl
  • bootstrap.pl
  • diagnose.pl
  • install.pl
• You can now configure the proxy.pass setting for the Linux Collector during the installation process:
  • It will also be automatically encrypted through the installer.
  • If you need to add it to agent.conf in plaintext later, it will be automatically encrypted.
  • If you already have it, it will also be automatically encrypted during upgrade.
• Upgraded the following:
  • Postgresql to 42.2.20
  • json-smart to 2.4.7
  • bcprov-jdk15on to 1.69
  • jaxb-runtime to 2.3.2
  • commons-compress to 1.21
  • jetty-http to 9.4.43
  • jsoup to 1.14.2
  • JRE to 11.0.12.7.1

Bug Fixes

• LM Logs now properly parses RFC 5424 timestamps.
• LM Logs now supports RFC 6587 format over Syslog.
• Collector Size dropdown now shows default Collector size when installing on Windows.
• Fixed an issue that caused Docker Collectors to go into endless reboot on upgrade.
• Fixed an issue that prevented scheduled execution of ERI PropertySources, affecting Topology.
• Fixed an issue where multiple Windows Events were dropped if one failed to be retrieved for EventSources.
• Fixed LogicMonitor text on Windows installer.
• NetFlow now properly parses DSTASN and SRCASN fields.
• Fixed an issue where JDBC task response time returns “NaN” when it should return “0”.
• Fixed an issue where diagnose.ps1 failed to run on PowerShell 3.0.
• Fixed an issue that caused remote sessions to fail if using a Collector proxy and only whitelisting the relay server’s hostname (and not the IP address).
• Fixed an issue where NetFlow packets would be dropped if ltoo many NetFlow export devices were pointed at a given Collector.

Known Issues

• If the EA Collector 30.103 was installed on Windows silently via PowerShell or CMD, upgrading to EA 30.104 will fail. This issue does not occur for Windows Collector installation and upgrade via the UI-based install wizard.

MGD Collector 30.001

The general deployment GD Collector 30.001 has been designated as the next minimum general deployment version, MGD Collector 30.001.

The automatic update to MGD Collector 30.001 will deploy on January 10, 2022. This release, which was scheduled for deployment on October 27th, was postponed while we fixed a performance issue. User action is not required ahead of this date, but we recommend that you update to MGD Collector 30.001 as soon as possible. For more information about the deployment schedule, see MGD Release Update.

Highlights

MGD Collector 30.001

Upgrading to MGD Collector 30.001, or optionally EA 30.xxx, will give you access to many new features and fixes highlighted below.

• MGD Collector 30.001 will be the first MGD Collector version to use JDK 11.

Other highlights include all of the new features introduced in the EA Collector 29.xxx versions, as well as many fixes and optimizations:

• Support for LM Logs.
• SSE enhancements.
• Updated Java JARs.
• NBAR slots support for direction, IPv6, and Application.
• Collector sizes XL and XXL.
• Collector Script Cache.
• Scripts to enable migration from root/Administrator to non-root and non-Administrator user for running the Collector.

For a complete list of new features and fixes across all Collector versions, see Collector Versions.

EA Collector 30.xxx

For early access to additional features, you may consider upgrading to one of the EA Collector 30.xxx versions. Because early access versions are updates that contain new beta functionality, they are not recommended for your entire infrastructure. Features in EA Collector 30.xxx include:

• Support for OpenMetrics Collection.
• Open Beta support for Credential Vault integrations, using CyberArk and Thycotic.
• Support for forwarding Windows Event Logs and Kubernetes Events to LM Logs.
• Capability for changing the Collector Size setting during installation, after download.

GD Collector – 30.001

LogicMonitor GD Collector 30.001 was released on August 23, 2021 and includes the following changes.

Fixes

• Fixed an issue with the commons-codec library that was causing issues with updated collectors.
• Fixed issue with MongoDB driver dependencies. It is now properly upgraded to version 4.1.0

Known Issues

• Upgrading from EA Collector 28.604 to EA Collector 30.000 will fail. We recommend upgrading to GD Collector 30.001 before you upgrade to an EA 30.xxx version.

Developer

• We provide Java classes to help you develop your own LogicModules. These Java classes include SNMP, Expect, and so on. See the Javadoc for EA Collector 30.101.

EA Collector – 30.102

LogicMonitor EA Collector 30.102 was released on July 20, 2021 and includes the following updates and fixes.

Enhancements

• ADDED Beta Support for the new Thycotic Secret Server Integration. It works similar to the CyberArk integration and shares most of the same functionality. See the Credential Vault for LM Collector.
• IMPROVED the Credential Vault Integration to require less frequent polling of CyberArk and Thycotic servers.
• ADDED NetFlow support for more BGP ASN related fields and VeloCloud fields.
• ADDED support for defining a backup resource to associate logs to when mapping fails. One backup resource can be defined per collector, and all logs that fail to map to its resource for any reason, will be mapped to this backup resource.
• IMPROVED LM Logs to properly parses host and IP info from Fortinet device logs.
• IMPROVED Collector events to include why syslog ingestion failed due to mismatched collector configuration and resource property.
• CHANGED the default setting of the Collector property enable.eof.exception.handling to true.
• CHANGED the Collector Size setting to allow changes after download. It will default to whatever is selected in the UI during download. If you don’t have enough memory for that size, or decide you want a different size, you can change the selection at install time.
  • On Linux, you can use the ‘-s’ flag or answer during the prompt.
  • On Windows, you’ll see the option in the installer steps.
• UPDATED the following JAR files:
  • json-smart 2.2.1 to 2.4.2
  • accessors-smart 1.1 to 2.4.2
  • asm 5.0.3 to 8.0.1
  • slf4j-api  1.7.16 to 1.7.30
  • json-path 2.2.0 to 2.5.0
  • jetty-util 9.4.37.v20210219 to 9.4.39.v20210325
  • netty-all 4.1.58.Final to 4.1.61.Final
  • commons-io 2.6 to 2.8.0

Fixes

• FIXED an issue where Windows Event Logs copied from Applications and Services Logs were not properly being ingested by EventSources.
• FIXED !vbscript debug command to print out the proper script path.
• FIXED an issue where some logs were not being ingested if the resource was not monitored by the same Collector configured for syslog collection.
• FIXED Windows EventSource Test functionality to properly show filtered events.
• FIXED an issue where Windows Collector upgrades would fail if the Collector service was not properly stopped.
• FIXED an issue with floating point data not being properly ingested from batchscript output.
• FIXED /etc/ld.so.conf.d/logicmonitor-collector-jre.conf so it is no longer owned by root if the Collector is not installed as root.

Developer

• We provide Java classes to help you develop your own LogicModules. These Java classes include SNMP, Expect, and so on. See the Javadoc for EA Collector 30.101.

EA Collector – 30.101

LogicMonitor EA Collector 30.101 was released on June 9, 2021 and includes the following updates.

Updates

• ADDED support for High Security mode (HSM). Users can choose to install in HSM or Orchestration Compatibility Mode (OCM). The default is OCM. 
  • HSM changes the permissions on the Collector installation folder so that only the owner and root/Administrator can access it.
  • OCM allows non-admin users to access the Collector installation folder. This is useful for users who may be using an orchestration utility to manage agent.conf or anything else in the Collector folder.
• ADDED encryption to selected agent.conf properties.
• ADDED functionality to override openmetrics.url property with openmetrics.host or system.hostname properties when the URL isn’t provided.
• CHANGED the timestamp field to be enabled and set to true by default.
• FIXED an issue where instance groups were not being created for OpenMetrics instances.
• FIXED an issue where company.uuid was not encrypted when the Windows Collector was installed in silent mode.

Known Issues

• A privileged LogicMonitor user cannot use the !getconfig debug command to retrieve credential and company.uuid value.
• Users cannot initialize the HSM mode for a Windows Collector that is installed as a non-Administrator user.
• Upgrading from EA Collector 28.604 to EA Collector 30.000 will fail. We recommend upgrading to GD Collector 30.001 before you upgrade to an EA 30.xxx version.

Developer

• We provide Java classes to help you develop your own LogicModules. These Java classes include SNMP, Expect, and so on. See the Javadoc for EA Collector 30.101.

GD Collector – 30.000

GD 30.000 incorporates all enhancements and fixes found in GD 29.003, as well as EA 29.xxx (29.101, 29.102, 29.104, 29.105, 29.106, 29.107, 29.108, and 29.109).

Updates

Here are a few highlights across the various EA 29.xxx releases that GD 30.000 contains.

• NBAR support for NetFlow.
• LM Logs support.
• Non-root installation no longer depends on sudo.
• The Collector Script Cache.
• Updated Amazon Corretto Java to 11.0.10.9.1.
• Fixed an issue where the Collector would intermittently stop forwarding syslog logs to LM Logs.

For a complete list of changes, visit the individual release notes pages for the various releases.

Known Issues

• When a Collector is installed and restarted before calculation of SHA (collector.service.controller.SHA in agent.conf), the watchdog services won’t run. Users must wait approximately 2 minutes after installation for SHA to be calculated for the first time before they restart the Collector. After this, future restarts should not cause an issue.

EA Collector – 30.100

Changes

• Added an agent.conf directive (vault.credentials.refresh.delay) to control the Credential Vault integration cache expiration refresh delay.
• Added JMX metrics for monitoring the CyberArk AAM Credential Vault integration.
• Added two agent.conf properties (sse.collectorgroup.jvm.locale and collector.jvm.locale) to allow tweaking of JVM locale, which is sometimes needed to correct date parsing in some locales. The default for both properties is “en_us”.
• Added obfuscation to the password length in log messages.
• Add metrics to LM Logs Collector DataSource to monitor the performance of the new Windows Event Log integration.
• Added resource mapping logic in LM Logs to use the socket address when hostname is not present for Cisco syslog events.
• Added a new configuration discover.instance.wmi.timeout.seconds for the timeout that is explicitly used in case of adding additional monitoring. The default value of the property is 30s. The property is not added by default in the agent.conf. Customers who face the timeout issue can add this property with the desired timeout value.
• Added agent.conf directive webpage.circular.redirect=false to allow circular redirect following by the WEBPAGE Collector.
• Added support for sFlow v1 and v5 for IPv6.
• Added support for new OpenMetrics collection.
• Added support for filtering by ##DESCRIPTION## in Script ActiveDiscovery.
• Improved Logfile task scheduling after Collector restart.
• Updated to Amazon Java Corretto 11.0.10.9.1.
• Updated the Collector to use G1 garbage collector, instead of the deprecated CMS garbage collector.

Fixes

• Fixed an issue where the Collector would intermittently stop forwarding syslog logs to LM Logs.
• Fixed vulnerabilities in xmlrpc-client-3.1.jar and xmlrpc-common-3.1.jar.
• Fixed an issue where JDBC collection would fail if the username contained a whitespace.
• Fixed an issue with Cisco ASA initiator and responder packet fields in traffic flows. Some ASAs were not showing traffic information in NetFlow.
• Fixed the Collector debug command !snmpdiagnose to now support SNMPv3 with AuthNoPriv mode.
• Fixed proxy.port assignment to properly take the value given in the installer.
• Fixed batchscript collection to properly distinguish instances that share names up to the first period. Previously, “test.test.1” and “test.test.2” were seen as one instance.