Collector Release Notes Timeline

EA Collector 33.300

LogicMonitor EA Collector 33.300 is released on February 22, 2023. It is based on the previously released EA Collector 33.200 and includes the following additional updates.

Enhancements

• Added the service.read_timeout_getconf property to the agent.conf setting. It specifies the HTTP read timeout for getConf API call made by collector to the Santaba server.
• Enabled IPFIX NBAR data collection as per RFC-6759. It thus enables Application_ID detection from the Scope field of the Optional template which is part of the IPFIX NBAR flow.

Fixed Issues

• Upgraded version of the following files for various minor security updates.

• Fixed an issue where after upgrading to GD 33.001, certain datasources, if timed out during active discovery, led to an exception and exited the SPSE threads. As a result, the custom PowerShell scripted PropertySources and core LogicModules started to fail.

GD Collector 33.002

LogicMonitor GD Collector 33.002 is released on February 20, 2023. GD Collector 33.002 is a patch to the previously released GD Collector 33.001 and includes the following additional updates:

Enhancement

• The current SPSE thread count is minimum 3, maximum 10, and queue size is 10. Due to this, at a time, only 10 PowerShell processes are run, additionally 10 stay in a queue, and the remaining processes are dropped. To overcome this shortcoming, we have increased the thread count of collectors of different sizes as follows:

Fixed Issues

• Fixed an issue where as part of GD 33.001 upgrade, when AWS SDK was upgraded to version aws-java-sdk-s3-1.12.264, certain AWS related datasources started to fail as the upgraded version of S3 jar was not backward compatible.
• Fixed an issue where although collector was up and running, it did not collect data and collector status was reported as down.
• Fixed an issue where after upgrading to GD 33.001, certain datasources if timed out during active discovery led to an exception and exited the SPSE threads. As a result, the custom PowerShell scripted PropertySources and core LogicModules started to fail.
• Fixed an issue where after upgrading to GD 33.001, for Linux non-root collector, the watchdog did not start and displayed errors when attempting to start agent and watchdog.
• Fixed an issue where when you upgrade collector version from MGD 30.xxx, GD 31.xxx, or MGD 31.004 and later to collector version GD 33.001, the custom JAR files were reported to be lost or missing. When you downgrade the collector from GD 33.001 to any version between EA 31.100 to EA 32.100, the downgrade failed.

EA Collector 33.200

LogicMonitor EA Collector 33.200 is released on January 16, 2023. It is based on the previously released EA Collector 33.101 and includes the following additional fixes.

Fixed Issues

• Upgraded version of the following files for various minor security updates.

• Fixed an issue where IPMI datasource could not collect data due to missing libeay32.dll file. Similarly, iDRAC monitoring did not work due to poll timeout issue. After upgrading ipmiutil to version 3.1.8, we have fixed both the issues.
• Fixed an issue where while installing collector in docker, the collector provided incorrect installation logs when installation failed due to insufficient memory.

EA Collector 33.101

LogicMonitor EA Collector 33.101 is released on November 24, 2022. EA Collector 33.101 is a patch to the previously released EA Collector 33.100 and includes the following additional fix:

Fixed Issue

• After upgrading to EA Collector 33.100, core LogicMonitor or custom-created modules that do not properly close Oracle connections accumulate inactive sessions that can affect Oracle database performance and availability. To handle this issue, update core LogicModules to the most recent version (as of November 10, 2022) and audit any custom modules creating Oracle connections. As a precautionary step to mitigate the risk of performance and availability impact on production Oracle environments, we have temporarily rolled back the jar from version 21.5.0.0 to 11.2.0.3.0.

GD Collector 33.001

LogicMonitor GD Collector 33.001 is released on November 23, 2022. GD Collector 33.001 is a patch to the previously released GD Collector 33.000 and includes the following additional fixes:

Fixed Issues

• After upgrading to GD Collector 33.000, core LogicMonitor or custom-created modules that do not properly close Oracle connections accumulate inactive sessions that can affect Oracle database performance and availability. To handle this issue, update core LogicModules to the most recent version (as of November 10, 2022) and audit any custom modules creating Oracle connections. As a precautionary step to mitigate the risk of performance and availability impact on production Oracle environments, we have temporarily rolled back the jar from version 21.5.0.0 to 11.2.0.3.0.
• Upgraded Apache ivy to version 2.5.1, netty-common to version netty-common-4.1.79.Final jar, and aws-java-sdk-s3 to version aws-java-sdk-s3-1.12.264 jar for various minor security updates.
• Fixed an issue where Active Discovery scripts behaved differently and failed to collect data when evaluating an undefined property (for example, host property does not exist). To fix the issue, we introduced HostProps as an environment variable. Active Discovery scripts can now collect data even if property does not exist.
• Fixed an issue where the WMI password in plaintext format was displayed in a text file in collector machine when Windows collector executed PowerShell script for active discovery. We immediately fixed this issue and the WMI password is no longer displayed as plaintext.

EA Collector 33.100

LogicMonitor EA Collector 33.100 is released on November 15, 2022 and includes the following updates.

Enhancements

• Upgraded aws-java-sdk-s3 jar to version aws-java-sdk-s3-1.12.264.
• Upgraded hsqldb jar to version 2.7.1.
• Upgraded netty-common-4.1.63.Final jar to version netty-common-4.1.79.Final.
• Upgraded jsoup to version 1.15.3.
• Added LogSource logging support in Collector for logsource.kubernetes and logsource.collectoringestapi components. You can access them on the Manage Collector Logs page on the UI.
• Added property enable.netflow.parallel.execution to considerably reduce the Netflow packet drop issue. By default, the property is set as true. With this enhancement, you can observe negligible packet drops.
• Forwarding Windows event logs to LogicMonitor logs is now supported only through LogSources. We no longer support log forwarding through lmlogs.windowseventlogs.enabled property in agent.conf and lmlogs.winevents.enable (custom) property in the monitored device.
• Prior to this release users had to add the include filter to get the information level logs. To help users, we now support information level logs by default for WMI logsource.
• Added the following counters to Collector DataSource LogicMonitor_Collector_LMLogs for log collection performance monitoring. This will help clarify the present count during device usage and post consumption after increasing the value of these parameters:
  • lmlogs.thread.count.for.ingest.api.communication
  • eventcollector.wineventlog.threadpool
  • eventcollector.wineventlog.max.eventitem
  • eventcollector.syslog.threadpool
  • eventcollector.syslog.queue
• The value of logcollector.wineventlog.max.eventitem  was by default set to 500 for all collector sizes. We have now updated it to suit collectors of all supported sizes.

Fixed Issues

• Fixed an issue where while processing the Syslog message sent to Collector, the initial string were getting trimmed and as a result, the regexnotmatch filter did not work as expected for Syslog LogSources.
• Fixed an issue where Collector read the entire log file multiple times and as a result created duplicate alerts.
• Fixed an issue where Active Discovery scripts behaved differently and failed to collect data when evaluating an undefined property (for example, host property does not exist). To fix the issue, we introduced HostProps as an environment variable. Now, Active Discovery scripts can collect data even if a property does not exist.
• Fixed an issue where internal webcheck failed to follow redirect for http code 308.
• Fixed an issue where some of the Windows event logs were missing on the LogicMonitor Logs page when LogSources were used for collection.
• Fixed an issue where the remote session did not stop from collector-side. To fix this issue we added remotesession.timeout.seconds property to agent.conf. Its value defaults to 600 seconds and supports minimum 300 seconds. However, we recommend that you set it to less than or equal to 1800 seconds.
• Fixed an issue where using the regex method for resource mapping in LogSource, while performing the regex operation on the Message field of the Syslog event, the messages were trimmed and partial value was sent. As a result, the regex operation was applied only to the partial match. To fix the issue, we now perform the regex operation on the rawMessage field of the Syslog event which ensures that the entire event is sent without trimming.
• Fixed an issue where WMI password in plain text was exposed in the Event viewer during Poll Now. We have masked the password to strengthen its security.

Known Issue

• You might observe that during WMI log collection some logs are missing/duplicate around the time when collector restarts, and hence, on the Logs page the total logs count does not match when compared with the expected logs generated from devices.

GD Collector 33.000

LogicMonitor GD Collector 33.000 is released on November 10, 2022. EA Collector 32.400 has been designated as GD Collector 33.000 and includes the following additional updates:

Enhancement

• Upgraded hsqldb jar to version 2.7.1 to mitigate CVE-2022-41853 vulnerabilities.

Fix

• Fixed an issue where wmi password in plain text was exposed in the Event viewer during Poll Now. We have masked the password to strengthen its security.

GD Collector 32.004

LogicMonitor GD Collector 32.004 is released on November 01, 2022. GD Collector 32.004 is a patch to the previously released GD Collector 32.003. This patch release mitigates the following high severity issue.

Fix

• Fixed an issue where wmi password in plain text was exposed in the Event viewer during Poll Now. We have masked the password to strengthen its security.

EA Collector 32.400

LogicMonitor EA Collector 32.400 is released on September 22, 2022 and includes the following updates.

Enhancements

• Upgraded Corretto JRE version to 11.0.16.8.1 to mitigate Xalan (XSLT) parsing vulnerability CVE-2022-34169.
• To resolve the delay in log ingestion, we removed the synchronisation added to send logs to ingest API. We also verified that the existing flow of logs is working.
• If the updateToNonRoot.sh script fails to migrate Linux Collector from root to non-root, or if there are any issues after migration, customers can now run the revertToRootUser.sh script to roll back migration. The script is available in the agent/bin folder.
• As most of the customers do not use jt400-full-6.0.jar (IBM iSeries/AS400 JAR) in core LogicMonitor DataSources to monitor IBM I series databases, we have removed support for this file.
• Since mail.jar is rarely used in Collector, we removed it from Collector codebase. We replaced it with jakarta.mail-2.0.1.jar.
• The Synthetics Selenium collection will now retry all commands rather than a specific subset, so that customer tests will be more resilient to failures due to minor timing discrepancies. Also, instead of maintaining multiple jars of the Synthetic library, we have now consolidated them in an all-in-one jar in the synthetics-monitoring-all-in-one:1.0.0-RC2.
• Improved the Enhanced Script NetScan feature by enabling NetScan to assign a single device to multiple resource groups.
• Collectors can receive SNMP traps, but they can only use one SNMP community string (V1 and V2C) or a set of credentials (V3) to decrypt the traps. This does not work if users have multiple systems sending traps with different community strings to the same Collector. To bridge this gap, users can now override eventcollector.snmptrap.* by setting that as a host property on the device. Collector will first check for the host property before checking agent.conf when decrypting a trap. If it is not specified in the host property, then it falls back on agent.conf eventcollector.snmptrap.*
• We added LM Log: Script type to LogSources. Using Groovy script you can now collect logs from scripts/APIs and send them to LogicMonitor. There is no need to separately create datasources to send logs from scripts to LogicMonitor. Instead, you can directly use Script LogSource for the same.
• It was reported that MBeans are not queried successfully because Collector does not support the first level attributes that contain dots, for example, jira-software.max.user.count. Collector treated it as composite attribute and split it based on the dots. To instruct Collector not to split the attribute, we added a backslash ( \ ) before a dot (.) such as jira-software\.max\.user\.count

Fixes

• It was reported that the currently used PostgreSQL JDBC jar version 42.3.2 is vulnerable to CVE-2022-31197. We therefore upgraded PostgreSQL JDBC jar to version 42.4.1.
• Fixed an issue where redundant data was concatenated during polling using Windows and Linux Collector for OpenMetrics. 

GD Collector 32.003

LogicMonitor GD Collector 32.003 is released on September 20, 2022. GD Collector 32.003 is a patch to the previously released GD Collector 32.002. This patch release mitigates the following high severity issue.

Fix

• After upgrading Collector from EA Collector 29.106 (or prior version) to MGD Collector 31.004, when you upgrade it to GD Collector 32.002, the upgrade fails with a null pointer exception. We have applied a fix to resolve this issue.