LogicMonitor + Catchpoint: Enter the New Era of Autonomous IT

Learn more

Release Note

Collector Release Notes Timeline

December 19, 2023

EA Collector 35.100

LogicMonitor EA Collector 35.100 is released on December 19, 2023. It is based on the previously released GD Collector 35.000 and includes the following additional updates.

Updated on December 21, 2023

Added – An update about linux collector installation using non-root user.

(more…)

December 18, 2023

GD Collector 35.000

LogicMonitor GD Collector 35.000 is released on December 18, 2023. It is based on the previously released EA Collector 34.500 and includes the following additional updates.

(more…)

November 01, 2023

EA Collector 34.500

LogicMonitor EA Collector 34.500 is released on November 01, 2023. It is based on the previously released EA Collector 34.400 and includes the following additional updates.

(more…)

October 16, 2023

GD Collector 34.004

LogicMonitor GD Collector 34.004 is released on October 16, 2023. It is a patch to the previously released GD Collector 34.003 and includes the following additional fix.

(more…)

October 06, 2023

MGD Collector 33.007

LogicMonitor MGD Collector 33.007 is released on October 06, 2023. GD Collector 33.007 is designated as MGD Collector 33.007, and includes the following updates:

(more…)

October 05, 2023

EA Collector 34.400

LogicMonitor EA Collector 34.400 is released on October 05, 2023. It is based on the previously released EA Collector 34.300 and includes the following additional updates.

(more…)

September 18, 2023

GD Collector 34.003

LogicMonitor GD Collector 34.003 is released on September 18, 2023. It is a patch to the previously released GD Collector 34.002 and includes the following additional updates.

Updated on October 17, 2023

Removed – Fixed an issue where the script for PropertySources failed due to credential vault enhancements done in the previous release.

You can get this fix in GD Collector – 34.004

Enhancement

  • The Selenium Synthetics Step Monitoring feature is added to GD Collector 34.003. To access this feature, you must have Platform v.187 (or later) and GD Collector 34.003. With this feature every Synthetics web test is represented as a resource in LogicMonitor. A web test is further divided into steps and collector monitors the steps to give accurate status of each step.

Fixed Issue

  • Fixed an issue where after upgrading Linux collector to GD Collector 34.002, the value in the Service Group field was overwritten. This prevented Logicmonitor-agent service from starting when the group was non-existent. After implementing the fix, Logicmonitor-agent service is able to start successfully. This is applicable only to collectors running as non-root, and where the non-root username and group name are different.

September 04, 2023

GD Collector 33.007

LogicMonitor GD Collector 33.007 is released on September 04, 2023. It is a patch to the previously released GD Collector 33.006 and includes the following additional fix.

Fixed Issue

  • Fixed an issue where when updating Linux collector to GD Collector 33.006 the Service Group field was overwritten after the collector upgrade. This prevented the Logicmonitor-agent service from starting when the group was non-existent. After implementing the fix, the Logicmonitor-agent service is able to start successfully. This is applicable only to collectors running as non-root, and where the non root username and group name are different.

August 07, 2023

EA Collector 34.300

LogicMonitor EA Collector 34.300 is released on August 07, 2023. It is based on the previously released EA Collector 34.200 and includes the following additional updates.

Enhancements

  • It was observed that because there was no configuration for the maximum number of threadpool, it was limited to a minimum number of threadpool. Also, the queue limit for the Windows event tasks was not defined. To bridge the gap, we added the following parameters along with the queue size.
LogSource TypeWinEventSyslog
Min thread pool size parameter(existing)logcollector.wineventlog.threadpooleventcollector.syslog.threadpool
Max thread pool size parameterlogcollector.wineventlog.max.threadpooleventcollector.syslog.max.threadpool
Queue sizelogcollector.wineventlog.queueeventcollector.syslog.queue (existing)

The values vary as per the collector size. 

Collector SizeMinimum ThreadpoolMaximum Threadpool Queue Size
Small/ Nano102010000
Medium103010000
Large104010000
X-Large105010000
XX-Large106010000
  • We have improved the Heap and Non-heap memory of small and medium size collectors for SNMP v2c. 
    • Medium size collectors – Added wrapper.java.additional.24=-XX:MaxMetaspaceSize=756m to wrapper.conf 
    • Small size collectors – Added wrapper.java.additional.24=-XX:MaxMetaspaceSize=128m to wrapper.conf. Updated wrapper.java.maxmemory=1024 (old value) to wrapper.java.maxmemory=756 (new value)

Fixed Issues

  • Upgraded version of the following JAR for a minor security update.
Current JAR VersionUpgraded JAR Version
jose4j-0.7.10jose4j-0.9.3
wildfly-elytron2.2.0.Final
  • Fixed an issue where spaces in the script path used in the Windows wrapper javascript command arguments led to errors. To fix the issue, you can now use a placeholder in the command line argument. The placeholder is prefixed with a dollar sign ($) and the name and value of the placeholder is passed as an optional argument. Optional argument must follow the format: "<Placeholder Name>=<Value>"
    For example,
cscript.exe C:\lmbatchjobwrapper.js 10.1.1.1:7214 host myJob "powershell.exe -file $arg1" "arg1=C:\Program Files\Test Space Folder\Powershellcmd2.ps1"
PowerShell

Here, arg1 is the placeholder( $arg1 ) used in the command line argument and "arg1=C:\Program Files\Test Space Folder\Powershellcmd2.ps1" is the optional argument.

July 03, 2023

GD Collector 33.006

LogicMonitor GD Collector 33.006 is released on July 03, 2023. It is a patch to the previously released GD Collector 33.005 and includes the following additional fix.

Fixed Issue

  • Fixed an issue where when you upgrade a collector, the obsolete CAs were re-imported in the upgraded JRE. AWS adds and removes the CAs from the cacert file of JRE mostly in every release. With the fix that we have implemented, the obsolete CAs will not be re-imported in the upgraded JRE.
1 2 4 5 6 13 14

14-day access to the full LogicMonitor platform