Early Release Collector – 20.059

Last updated on 14 September, 2022

The 20.059 Early Release collector has a number of optimizations and fixes.  It will be available the week of November 30, 2015.

New Features:

  • The Java Service Wrapper under which the collector runs has been replaced with YAJSW.This change addresses both a potential memory leak situation and allows for better collector troubleshooting. Additionally, the YAJSW wrapper provides more flexibility and support for future collector enhancements.
  • Windows collectors now support embedded PowerShell scripting in datasources. The embedded PowerShell feature behaves just like embedded groovy scripting, in that PowerShell can be used both in Active Discovery and datapoint collection scripts. In the collector debug window there’s now a !posh command for testing PowerShell scripts that’s analogous to the existing !groovy command. Existing datasources using external PowerShell scripts (using the upload functionality) will continue to behave as always.
  • The EA collector supports metrics for three new datasources, Data Collecting Task, Event Collecting Task, and Collector Status.  These datasources provide metrics regarding how many instances a collector is monitoring, it’s current version, uptime, and task counts.

Note: We previously announced a new script collection method for Eventsources – bugs have since been identified and, as a result, this feature will be included in the next early release collector.


  • More accurate status information when data collection is initializing for perfmon datasources.
  • Utilization of TLS 1.2 for reporting data back to LogicMonitor as well as for webpage and CIM collection tasks.
  • Added validation for EventIDs in event datasources, including a maximum value of 65536
  • Added support for collector installations on newer versions of Ubuntu, RedHat, Centos and other operating systems using systemd.
  • The collector will determine if a monitored device has a collector installed on it.  If so, the collector datasources will automatically apply.
  • Added timeouts to collector initialization operations to avoid the collector watchdog tasks stuck in a starting state.
  • Added additional netapp configurations (netapp.connection.concurrency# and netapp.connection.threadPoolSize)  to manage the number of concurrent requests allowed to a netapp host.
  • Minor netflow improvements to handle empty flows and delays in data refreshing
  • Improvements on how WMI reports no data, better distinguishing between the device not returning data and the collector having issues reporting data

Bugs Fixed:

  • An empty auto discovery parameter was causing auto discovery to fail.
  • Update to the latest version of the IPMIutil.exe utilized by datasources..  The previous version had known bugs that could impact data collection.
  • Fix to correctly process NaN in complex datapoints, enabling conversion of NaN to 0
  • Glob was not accurately supported for windows file names in Logfile EventSources.
  • Fixed an issue with the event collector to support batch job alerts that were receiving access not allowed errors.
  • Any string returned via perfmon would cause all datapoints to be reported as NaN.
  • If netflow collection initialized during other collector processes, it was possible the script could be terminated.  This potential conflict has been removed.
  • Data collection via IMPI was not working on a 32 bit windows collector for collector version GD 20.
  • Added the ability to manually disable event collectors.  Previously this change could be made in the collector but did not take effect.
  • If a network error occurs during a script download for a datasource, the previous version will persist.
  • A previous JDK upgrade caused an issue with AWS EC2 Netscan policies, the Netscan processing has been adjusted to account for the conflict. 

Note:  If the IP address of the device your collector is installed on is associated with multiple devices, for example if you are using a Docker container or MS Clustering, this collector version is not recommended.  Collector datasources will be applied to all devices associated with the IP, potentially resulting in false alerts.  This will be resolved in the next EA collector, expected soon.