LogicMonitor GD Collector 34.002 is released on June 29, 2023. It is a patch to the previously released GD Collector 34.001 and includes the following additional fixes.

Fixed Issues

• Fixed an issue where when you upgrade a collector from GD 34.000 (installed as a non-root user) to GD 34.001, the ping DataSource (DS) stopped working. Certain binaries lacked the required capabilities to perform the ping operation as the upgrade is performed by a non-root user. To fix the issue, we added a new binary setnetcapraw. For the ping DS to work in an upgrade scenario from any collector version to GD 34.002 for non-root docker, run the command sudo setcap cap_setfcap+eip setnetcapraw in the <Agent_Root>/bin folder, and then restart the collector from the LogicMonitor portal. Note that you do not have to run this command when a freshly installed GD-34.002 is upgraded to a higher version.
• 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.

LogicMonitor EA Collector 34.200 is released on June 29, 2023. It is based on the previously released EA Collector 34.100 and includes the following additional updates.

Enhancements

• To enhance the WinRM configuration feature, we have introduced reversal logic for SDDL script to revert the changes done by WinRM_Config_01.ps1 and WinRM_Config_02.ps1 scripts. Example:
  • -Noninteractive -ExecutionPolicy Bypass -Noprofile -file \\10.55.21.12\To\WinRM_Config_01.ps1 -remove -UserName logicmonitor\ScriptTestUser01 -log True
  • -Noninteractive -ExecutionPolicy Bypass -Noprofile -file \\10.55.21.12\To\WinRM_Config_02.ps1 -remove -UserName logicmonitor\ScriptTestUser02 -log True
• To use a specific text from syslog in LogicMonitor logs as a metadata field, we have added a new method “Dynamic Regex Group” to SysLog LogSource field mapping. You can provide the field names separated by comma as ‘key’ and a common regex that has the same number of groups in it to capture these fields.

Fixed Issues

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

• Fixed an issue where WMI query was run with empty credentials. After applying the fix, WMI query will not run with empty credentials. Also, it will reuse the old credentials if the vault machine is down.

LogicMonitor GD Collector 34.001 is released on June 06, 2023. GD Collector 34.001 is a patch to the previously released GD Collector 34.000 and includes the following additional fix:

Fixed Issue

• Fixed an issue where even after upgrading to GD Collector 33.002, there was a spike in SPSE and PowerShell tasks timed out. To fix the issue of active discovery and data collection gaps in PowerShell modules, we have reverted the changes (addition of host properties to hashtable/environmental variables) introduced in GD Collector 33.001 that caused the performance issue.

LogicMonitor GD Collector 33.005 is released on June 06, 2023. GD Collector 33.005 is a patch to the previously released GD Collector 33.004 and includes the following additional fix:

Fixed Issue

• Fixed an issue where even after upgrading to GD Collector 33.002, there was a spike in SPSE and PowerShell tasks timed out. To fix the issue of active discovery and data collection gaps in PowerShell modules, we have reverted the changes (addition of host properties to hashtable/environmental variables) introduced in GD Collector 33.001 that caused the performance issue.

LogicMonitor EA Collector 34.100 is released on June 01, 2023 and includes the following updates.

Enhancements

• To enhance the security of customer data and LogicMonitor portal, and based on growing customer demand for reduction in privileges to run Windows collectors, we have developed Windows Remote Management (WinRM) based solution where Windows collectors are installed without administrator privilege. You can use this feature as part of the Open Beta program. For details, see Configuring WinRM for Windows Collector.
• On the Collector Status Page we have added a new module status SignatureValueChangedForHealthCheckScripts for collector health check scripts. It indicates whether the health check scripts are modified or not before they are run. If the scripts are not modified, the module status message indicates that the signature is verified successfully and the scripts are not modified. If the scripts are modified, the message indicates that the signature mismatch is found and the scripts are modified. The message also lists names of the modified health check scripts.
• Currently, a single set of credentials (for example, snmp.community, snmp.security, and so on) is applied on a device’s host property to receive SNMP traps (v1, v2c, and v3) and to collect data for SNMP DataSources that is SNMP polling. To support business requirements of multiple credentials, we have now separated credentials for SNMP traps and SNMP polling.
  • SNMP Polling – The current set of credentials/host properties for data collection are as follows: snmp.community, snmp.security, snmp.auth, snmp.authToken, snmp.priv, and snmp.privToken.
  • SNMP Traps – A new set of credentials/host properties to receive SNMP trap requests are as follows: snmptrap.community, snmptrap.security, snmptrap.auth, snmptrap.authToken, snmptrap.priv, and snmptrap.privToken. Because these properties are optional, if you do not define them, collector will continue to use snmp.* host properties to decrypt traps. This provision will also ensure backward compatibility.
• It was observed that collector installer carries multiple AWS SDK JARs which are used in the core and custom modules (DataSources). To ensure that the size of collector installer remains light, from now on, we will ship only the following AWS SDK JARs:
  • aws-java-sdk-core
  • aws-java-sdk-autoscaling
  • aws-java-sdk-ec2
  • aws-java-sdk-s3
  • aws-java-sdk-cloudformation
  • aws-java-sdk-cloudwatch
  • aws-java-sdk-dynamodb
  • aws-java-sdk-sqs
• As per the current design, when collector receives syslog event from an unmonitored device, the collector performs DNS resolution of all the devices monitored under it to check if any IP address matches with the IP of the syslog sending unmonitored device. In case of unmonitored devices, this method led to unnecessary DNS lookups and spike in DNS queries for every syslog event coming from the same unmonitored device. To overcome this challenge, we have optimised the design. Instead of doing the DNS resolution of all the monitored devices, collector will now do the DNS resolution of all the unmonitored devices only once and keep it in cache with configurable expiry time of 5 minutes. For subsequent syslog events from any unmonitored device, resource mapping will be done using this cache. In agent.conf setting, you can configure the expiry time in the lmlogs.syslog.unmonitored.device.cache.expiry.in.minutes property.

Fixed Issues

• Upgraded version of the following JAR for a minor security update.

• Fixed an issue where no data was collected in SNMPv3 because collector did not discover the engine ID at the time of actual data collection. To fix the issue, the SNMP engine ID will now be refreshed from SNMP4j cache on receiving null response from the device. If you insist on following the old behaviour of force cache clean, then in agent.conf, set snmp.datacollection.engineId.force.clean=true to refresh SNMP engine ID after every 10 minutes (default) interval. To configure this interval, in agent.conf, specify the duration in seconds in snmp.engineId.force.clean.intervalInSec property.
• Fixed an issue where after upgrading, the ping datasource failed to collect data and the ping debug command failed to display correct output.
• Fixed an issue where when you upgrade collector (that runs as root user) from version 28.004 to any version except EA 34.100 or GD 33.003 and then run the updateToNonRoot.sh script, the script failed due to the absence of the setnetcap file in the bin folder. To convert to non root user, you first upgrade to EA 34.100 or GD 33.003 that contains the setnetcap file in bin folder and then run the updateToNonRoot.sh script.
• Fixed an issue where when you upgrade a docker collector from root to non root using the UpgradeToNonroot.sh script, the script failed and led to errors. The error occurred because of the relative path in the UpgradeToNonroot.sh script:
  • -sf ./bin/logicmonitor-agent /etc/init.d/logicmonitor-agent
  • -sf ./bin/logicmonitor-watchdog /etc/init.d/logicmonitor-watchdog
    
    To fix the issue, we converted the relative path to absolute path by replacing “./” with “$DEST_DIR/agent“
    
  • -sf $DEST_DIR/agent/bin/logicmonitor-agent /etc/init.d/logicmonitor-agent
  • -sf $DEST_DIR/agent/bin/logicmonitor-watchdog /etc/init.d/logicmonitor-watchdog
    
    Also, because the UpgradeToNonroot.sh script is not designed for docker collector, if you try to run the script on docker collector, the system will stop running the script and display a warning message. 
• Fixed an issue where due to a bug Groovy script in SSE ran without being configured and consumed some memory. In the agent.conf setting, it was observed that even if the groovy.script.runner property is set to agent, it still picked SSE to run few collector health check scripts and internal web check in sitemonitor. To fix the issue, we have now ensured that SSE will not start if it is not set in the groovy.script.runner property.

LogicMonitor EA Collector 33.401 is released on May 23, 2023. EA Collector 33.401 is a patch to the previously released EA Collector 33.400 and includes the following additional update.

Enhancement

• To access the new Selenium Synthetics Step Monitoring feature, you must install Platform v.187 and EA Collector 33.401. 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. Note that if you do not upgrade to EA Collector 33.401, your existing Synthetics feature will stop working.

LogicMonitor GD Collector 34.000 is released on May 17, 2023. EA Collector 33.400 has been designated as GD Collector 34.000 and includes the following additional updates.

Enhancement

• Upgraded Snippet JAR from version 1.5.3 to 1.8.2

Fixed Issues

• Fixed an issue where collector stopped responding and reported that the HostStatus IdleInterval increased for all monitored hosts and created multiple HostStatus alerts. The issue occurred because ChronicleMap in the LiveHost file was used to monitor devices other than Meraki devices. Following this fix, if the groovy runner is agent, then by default, in-memory cache is used, thereby eliminating the possibility of cache corruption. If the groovy runner is SSE, and the LiveHost cache crashes due to corrupt cache file, then the system will find the corrupt cache file, delete it, and create a new one.
• Fixed an issue where the enable.netflow.parallel.execution property was missing in the agent.conf file when you upgrade collector form GD 33.001 to EA 33.100

LogicMonitor GD Collector 33.004 is released on May 02, 2023. GD Collector 33.004 is a patch to the previously released GD Collector 33.003 and includes the following additional fix:

Fixed Issue

• Fixed an issue where collector stopped responding, reported that the Host Status IdleInterval increased for all monitored hosts, and created multiple HostStatus alerts. The issue occurred because ChronicleMap in LiveHost was used for monitoring devices other than Meraki devices. Following this fix, if the groovy runner is agent, then by default in-memory cache is used, thereby eliminating the possibility of cache corruption. If you use groovy runner as SSE, and the LiveHost cache crashes due to corrupt cache file, then the system will find the corrupt cache file, delete it, and create a new one.

LogicMonitor GD Collector 33.003 is released on April 12, 2023. GD Collector 33.003 is a patch to the previously released GD Collector 33.002 and includes the following additional fixes:

Fixed Issues

• Fixed an issue where after upgrading, the ping datasource failed to collect data and the ping debug command failed to display correct output.
• Fixed an issue where the chronicle map of script cache crashed due to corrupt cache file and led to high CPU spike in collectors. As part of the fix, if the system finds a corrupt cache file, it is deleted.
• Fixed an issue where when you upgrade collector (that runs as root user) from version 28.004 to any version except GD 33.003 and then run the updateToNonRoot.sh script, the script failed due to the absence of the setnetcap file in the bin folder. To convert to non root user, you first upgrade to GD 33.003 that contains the setnetcap file in bin folder and then run the updateToNonRoot.sh script.
• Fixed an issue where when you upgrade a docker collector from root to non root using the UpgradeToNonroot.sh script, the script failed and led to errors. The error occurred because of the relative path in the UpgradeToNonroot.sh script 
  • -sf ./bin/logicmonitor-agent /etc/init.d/logicmonitor-agent and 
  • -sf ./bin/logicmonitor-watchdog /etc/init.d/logicmonitor-watchdog.
    To fix the issue, we converted the relative path to absolute path by replacing “./” with “$DEST_DIR/agent” 
  • -sf $DEST_DIR/agent/bin/logicmonitor-agent /etc/init.d/logicmonitor-agent
  • -sf $DEST_DIR/agent/bin/logicmonitor-watchdog /etc/init.d/logicmonitor-watchdog
    Also, because the UpgradeToNonroot.sh script is not designed for docker collector, if you try to run the script on docker collector, the system will stop running the script and display a warning message.

LogicMonitor EA Collector 33.400 is based on the previously released EA Collector 33.301. LogicMonitor EA Collector 33.400 is released on April 06, 2023 and includes the following updates.

Enhancements

• Added Add additional SNMP v3 Credentials checkbox under Advanced NetScan for the ICMP ping method to provide multiple SNMP v3 credentials. In scenarios where you have large networks with different SNMP v3 credentials per device, or cases where the credentials and devices are not mapped, you can enable this feature to let collector scan the devices and identify the correct SNMP v3 credential configured for it.
  Note that we have introduced this feature as part of open beta. To use this feature, you must first enroll for the beta program. To enroll and to get more details, contact your LogicMonitor Customer Support Manager.
• Configured the snmp.session.count.datacollecting property in the agent.conf to set the shared sessions count for SNMP v2c as per collector size:

• Enabled the hostProps environment variable for accessing device properties in the !posh debug command. It will help troubleshoot issues in the script and batchscript logicmodules.
• In Kubernetes collector, for the PortDiscoveryTask we can now use the host device IP to make host connection if the kubernetes.pod.hostNetwork property is enabled on the host.
• Improved the logging ability of the CollectorServiceController.txt log file when non root user starts, stops, or restarts collector.
• On the Collector Status Page we have added a new module status SignatureValueChangedForHealthCheckScripts for collector health check scripts. It indicates whether the health check scripts are modified or not before they are run. If the scripts are not modified, the module status message indicates that the signature is verified successfully and the scripts are not modified. If the scripts are modified, the message indicates that the signature mismatch is found and the scripts are modified. The message also lists names of the modified health check scripts.

Fixed Issues

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

• Fixed an issue where when SELinux is enabled, the updateToNonRoot.sh script failed while migrating collector from root to non root user.
• Fixed an issue where when vault properties are updated in the collector cache, all the existing tasks are removed and then rescheduled. This led to high CPU spike and issues during data collection. To fix this issue, when vault properties are updated, instead of rescheduling the existing tasks, the system reinitiates the tasks with updated vault properties.
• Fixed an issue where the chronicle map of script cache crashed due to corrupt cache file and led to high CPU spike in collectors. As part of the fix, if the system finds a corrupt cache file, it is deleted.
• Fixed an issue where when you use the updateToNonAdmin.ps1 script to migrate a collector running under user with administrator privileges to a domain user with non administrator privileges, the system erroneously indicated that the migration is successful, when in reality the collector had failed to migrate to non-admin user.
• Fixed an issue where when a new active discovery is made, the existing multi instance datasources displayed inconsistency in the number of times data is polled. The issue occurred due to the extra properties added to the DataSource instance object after scheduling the task in collector. After fixing the issue, there is consistency of polls in datasource.
• Fixed an issue where when you add special characters, backslash, or backtick to the host properties, the environment variable failed to run and as a result, PowerShell script crashed. As part of the fix, we have set all the host properties in a hostProps hash table. Customers can now directly access device properties.