Collectors Archives

You can schedule downtime (SDT) for your Collectors just as you can for your LogicMonitor devices. Creating SDTs for your Collector will suppress alert notifications for any Collector down alerts triggered during the SDT (these alerts will still be displayed in your LogicMonitor account). You may want to SDT your Collectors during maintenance windows or other periods of anticipated downtime. Note that if a Collector goes down while it is in SDT, it will still failover all assigned devices to the backup Collector, if one is assigned, and you will still be notified of this failover.

We separate Collector SDTs from general host/group SDTs in order to prevent unintended alert suppression stemming from your SDT’d Collector.

You can add an SDT that applies to one Collector or multiple Collectors from Settings | Collectors.

Adding an SDT for one Collector

Select SDT for the desired Collector, and then select Add SDT:

Adding an SDT for multiple Collectors

Check the box to the left of the desired Collectors and then select ‘Put in SDT’:

You can schedule a one-time SDT, or schedule a daily, weekly or monthly SDT. Add a note to an SDT to provide context for other users in the account.

You can see a list of events for your LogicMonitor Collector from Settings | Collectors. Typically the displayed events include errors related to data collection tasks and the stopping/starting/restarting of the collector services. Looking through these events can be helpful for debugging issues with your Collector.

To view Collector events, navigate to Settings | Collectors and locate the desired Collector. Select Manage, and then select Collector Events from the Support dropdown menu in the Manage dialog:

When you need to restart a Collector, you can do so from within LogicMonitor or from the Collector host.

Note: You can only use LogicMonitor to restart the Collector while it is up and running. If the Collector is down or dead, you will need to restart it from the Collector host.

Restart from LogicMonitor

To remotely restart a Collector from within the LogicMonitor platform:

1. Navigate to Settings | Collectors.

2. In the table, ind the Collector and click its Manage icon.

3. In the Manage Collector dialog, click Support and select “Restart Collector” from the menu.

Restart from Collector Host

On a Windows host. To restart a Collector, use the Services control panel to restart the following services:

LogicMonitor Collector
LogicMonitor Collector Watchdog

On a Linux host. To restart a Collector, run the following commands:

1. Stop LogicMonitor: /usr/local/logicmonitor/agent/bin/sbshutdown

2. Then start the watchdog service, which may be run from init.d or systemd.

From init.d: /etc/init.d/logicmonitor-watchdog start
From systemd: systemctl start logicmonitor-watchdog

Overview

Every Collector (that is not a member of an Auto-Balanced Collector Group) should have a failover Collector assigned to it. Failover Collectors eliminate the Collector as a single point of failure, ensuring monitoring continues should a Collector go down.

If a Collector is declared down (a Collector is declared down when LogicMonitor’s servers have not heard from it for three minutes), all devices monitored by the down Collector will automatically fail over to the failover Collector, assuming one is designated. Once the down Collector comes back online, failback can take place automatically (if automatic failback is enabled for the Collector) or manually.

Note: In addition to supporting the one-to-one Collector failover/failback method discussed throughout this support article, LogicMonitor also supports failover/failback within the context of Auto-Balanced Collector Groups (ABCGs). The Collectors in ABCGs share device load and support dynamic failover. For more information on ABCGs, see Auto-Balanced Collector Groups.

Designating a Failover Collector

Because the failover Collector will take over all monitoring for the down Collector, it’s important to ensure that the two Collectors (the original preferred Collector and the failover Collector) are well matched. In other words, the failover Collector must have the same data collection abilities and configurations as the original Collector. For example, both Collectors should be listed as exceptions for any firewalls restricting access to the monitors hosts; both Collectors must be permitted in any specific snmpd.conf, ntp.conf or other configuration settings that may limit monitoring access; and both Collectors must be on the same operating system (e.g. Linux or Windows).

For this reason, LogicMonitor recommends that you configure failover Collectors in pairs (i.e. Collector A fails over to Collector B and Collector B fails over to Collector A). As this recommendation implies, failover Collectors can also be assigned their own sets of monitoring tasks.

To designate a failover Collector:

Install/identify a Collector residing on a different server that is capable of monitoring the same set of devices as the Collector for which you are designating a failover Collector.
From the original Collector’s Manage Collector dialog (navigate to Settings | Collectors | Manage), select the failover Collector from the Failover Collector field’s dropdown menu.
Once a failover Collector is designated, two options display:
- Resume using Preferred Collector when it becomes available again. If left checked, automatic failback to the Collector is enabled, as discussed in the Automatic Failback to Original Collector section of this support article. If unchecked, failback will need to be manually initiated, as discussed in the Manual Failback to Original Collector section of this support article.
- Exclude <resource name> from failover actions. If left checked (recommended), the Collector device is excluded from failover. Because Collectors monitor themselves, this is most likely desirable as it will preserve Collector metrics.

Collector Failover

If a Collector is declared down, all devices monitored by the down Collector will automatically fail over to the failover Collector, assuming one is designated.

Note: A Collector is declared down and thus enters failover when LogicMonitor’s servers have not heard from it for three minutes. (The time window for initiating failover is governed by multiple, complex processes, and there may be slight differences in timing for different cases.)

Note: You will be notified of a Collector failover event even if the Collector is in SDT.

Collector Failback

Once the down Collector comes back online, failback can take place automatically (if automatic failback is enabled for the Collector) or manually.

Automatic Failback to Original Collector

To enable automatic device failback to the original Collector, navigate to the Collector’s Manage Collector dialog (Settings | Collectors | Manage) and check the Resume using Preferred Collector when it becomes available again option. As discussed in the Designating a Failover Collector section of this support article, this option is only available if a failback Collector is designated in the Failover Collector field.

Note: LogicMonitor will wait eight minutes after a Collector has resumed functioning to initiate automatic failback to it. (The time window for initiating failover is governed by multiple, complex processes, and there may be slight differences in timing for different cases.)

Manual Failback to Original Collector

If you choose not to enable automatic failback for a Collector, then you’ll need to manually reassign devices back to the original Collector once it is back online. This can be done by navigating to Settings | Collectors | Resources from either the original Collector that went down or the failover Collector.

When manually failing back from the original Collector’s resources list, you have the option to assign all devices back to the original Collector, or permanently assign them to the failover Collector.

When manually failing back from the failover Collector, you have a little more flexibility as you are able to fail back all or a subset of devices back to the original preferred Collector, as well as assign all or a subset of devices to any new preferred Collector. The ability to assign a Collector’s devices to a new preferred Collector can be done at any time; it is not limited to the aftermath of a failover event.

Overview

You can use the Collector Debug Facility to remotely run debug commands on your Collector. This is helpful for troubleshooting issues with data collection and is typically used on the advice of LogicMonitor support.

Note: The history of Collector debug commands is preserved in the Audit Log.

Accessing the Collector Debug Facility

There are two places from which you can launch the Collector Debug Facility:

From a Collector’s settings. As shown next, select Settings | Collectors, click the Settings icon for the Collector you would like to debug and, from the Support button’s dropdown, select “Run Debug” command.
From the Device Tree. Open the DataSource or DataSource instance that you would like to debug and from the Raw Data tab, click the Debug button.

Debug Command Syntax

The Collector Debug Facility launches in a new browser tab. A list of built-in debug commands and their descriptions display to assist with troubleshooting.

All debug commands should be preceded with a ‘!’. If you need syntax for a particular command, enter help !<commandname>, as shown next.

The following table highlights some of the most frequently used debug commands. For usage details (e.g. optional and mandatory arguments, parameters, etc.) and examples, enter the help !<commandname> from the Collector Debug Facility.

Command	Description	Example
!account	Displays the account information used by sbwinproxy.	!account
!adlist	Displays a list of the Collector’s Active Discovery tasks. A taskID is returned for each task.	!adlist type=get !adlist method=ad_snmp
!adetail <taskId>	Displays detailed information about a specific Active Discovery task, where taskId can be found with !adlist. Note that the “taskId” reference in the command specification will be labeled as “id” in the output of the !adlist command.	!adetail 142
!checkcredential	Enables, disables, and checks credential usage on the specified host to determine source of unexpected login action.	!checkcrendential proto=snmp user=public !checkcrendential proto=snmp user=public usage=AP
!hostproperty	Adds, updates, or deletes system properties for a host.	!hostproperty action=del host=localhost property=virtualization !hostproperty action=add host=localhost property=ips value=127.0.0.1,192.168.1.1
!http	Sends an HTTP request (with optional username and password) and displays the response.	!http http://www.google.com/index.html
!jdbc	Executes a SQL query against the specified host.	!jdbc ‘url=jdbc:mysql://productrds.chqwqvn285rf.us-west-2.rds.amazonaws.com:3306 username=LogicMonitor password=MyPassword’ select Name, ID from productDB.Employees
!logsurf	Displays log file entries that are of the specified debug level. If included, logs will only be displayed for the specified seq and taskId if they are in the specified file, and only n number of logs will be displayed. taskId and seq can be found using !tlist, where taskId is the id of a data collection task and seq is the number of times the collector remembers having done the task.	!logsurf level=trace ../logs/wrapper.log taskid=833 seq=75
!ping	Pings the specified host.	!ping 10.36.11.240 !ping type=proxy 10.36.11.240
!restart	Restarts the specified Collector service	!restart watchdog !restart collector
!shealthcheck func=<function> collector=<collector_id>	!shealthcheck commands help you determine the health of Collector, memory consumed, number of scheduled tasks, and more. Based on the result, you can debug the issues and resolve them. func=trigger This debug command triggers a healthcheck task for a specific Collector. Once you run this command, Santaba will schedule a healthcheck task for the specified Collector. To view the result, you must run !shealthcheck command with function func=detail or func=show. func=show Typically, you will find a summary of the scheduled task in the result. It also indicates the number of total, finished, and skipped healthcheck tasks. For example, “Latest run has finished. Scheduled checks (total=34, finished=27, skipped=7)” In case an issue is detected, the issue is summarised in the result. For example, “The disk has a low free space 728.57 MBytes.” You can run !shealthcheck func=detail collector=<collector_id> debug command to know the details of the issue or get details of the health status of a Collector. func=detail This debug command provides status of all the scripts in detail. For example, “Collector exported jars and executables are not modified.” “The Collector has 177 instances.” Once you run this command, Collector will display the result fetched by the func=trigger command. For example, for a specific Collector if you run the func=trigger command at 9.00 AM and then run func=detail at 11.00 AM, the Collector health status fetched at 9.00 AM will be displayed.	!shealthcheck func=show collector=123 !shealthcheck func=trigger collector=123 !shealthcheck func=detail collector=123
!tdetail <taskId>	Displays detailed information about a specific data collection task, where taskId can be found with !tlist.	!tdetail 12323209239991
!tlist	Lists the Collector’s data collection tasks, including DataSources, ConfigSources, and EventSources. A taskID is returned for each task.	!tlist c=wmi !tlist summary=collector !tlist summary=true lasttime=10 columns=5
!uptime	Displays the uptime of the Collector.	!uptime

Debug Example: Troubleshooting Data Collection

One of the most common uses of the Collector Debug Facility is troubleshooting data collection for a particular DataSource or DataSource instance. Maybe you just wrote a script DataSource and are getting NaN values, or perhaps one instance out of ten is not reporting data. You can typically use the following steps to identify the issue:

Identify the DataSource or DataSource instance. Find the name of the DataSource in the DataSource definition (this is NOT the same as the display name).
Use the !tlist command in the Collector Debug Facility of the collector associated with the device the DataSource applies to. You can narrow down the results by using the h=<hostname> and c=<collection type> options.
Identify the task for the desired DataSource. You’ll see the taskid, followed by an execution count, followed by the collector type, a status, the device name, then the DataSource name, an ival (which is the amount of time it took to execute the task the last time), and finally, a note about the execution.
Use the !tdetail command with the taskid as the argument.
If you need more information to diagnose the problem, increase the log level for the appropriate collection method of the Collector, as discussed in Collector Logging.
Wait a polling cycle (or more) and then use the !logsurf command with taskid as an argument and ../logs/wrapper.log as the filename (if you know the latest execution count, you can also limit the results to one operation by including seq=n). You can also include a number argument to limit the results to a certain number of logs. You should see the log entries only for the task whose id is included in the command.
If you still haven’t identified the issue, contact support.

From Settings | Collectors you can control how much information is logged by your collector and how long these log files are retained.

Adjusting log levels

You may want to adjust log levels to increase how much information is logged to debug an issue, or to decrease how much information is logged to save disk space. Select the Logs icon for the desired collector (from Settings | Collectors) and then select manage to see the log levels on a per component basis for that collector:

The log level for each collector component controls what information is logged for that component. Available log levels are:

trace – this log level is the most verbose, and will log every action of the collector in full detail. Note that this can use a significant amount of disk space if your collector is actively monitoring a large number of devices, and as such is typically only recommended for debugging purposes.
debug – detailed information about collector tasks will be logged (not as much information as trace log level). The debug log level can make it easier to identify an issue and track down the root cause.
info – this is the default log level, and will log basic information about collector tasks.
warn – information will only be logged when something isn’t quite right, but it may not be causing an issue yet.
error – information will only be logged when something is wrong.
disable – no information will be logged.

As an example, you might write a script datasource and your collector is getting no data, but you can’t figure out the problem. You could increase the log level for the collector.script component to debug or trace and then look at the logs (either using the collector debug facility or on the collector machine itself) to troubleshoot the issue.

Changing log file retention

Collector log files are rotated based on size, not date. By default, there are 3 log files of 64M each. If you’d like to change these numbers, you can do so in the wrapper.conf file (in the conf directory) where the collector is installed. You can edit the wrapper.conf file in the conf directory on the collector machine itself, OR you can edit the file directly from your LogicMonitor account UI. Navigate to Settings | Collectors and select manage for the desired collector. From the dropdown menu select Collector Configuration and then select the Wrapper Config tab. Locate the Wrapper Logging Properties and change these values (make sure to override the Wrapper.config before saving and restarting):

Sending logs to LogicMonitor

From the Manage dialog you can send your logs to LogicMonitor support. This might be useful if you are collaborating with our support team and would like them to be able to look through your collector log files. Select the manage gear icon for the desired collector and then select ‘Send logs to LogicMonitor’:

Logs that you’ve sent to LogicMonitor support will be displayed in the Logs section for that Collector. Filter based on time range to limit what is displayed:

To avoid downtime when moving your collector to another machine, we recommend that you install a new collector on the new machine and then transfer the monitored devices from the old collector to the new collector.

Once you’ve installed a collector on the new machine, you can transfer monitored devices to the new collector from Settings | Collectors. Simply locate the collector you’d like to transfer devices from, select the Devices (#) icon, select all devices (or a portion, if you don’t want to transfer all devices) and then select ‘Change Preferred Collector’:

Note: You should ensure that the new collector will have the same privileges as the collector it is replacing. For example:

are devices and networking gear configured to allow snmp access from the new collector device, or were they restricted to the old collector device’s IP address?
are database permissions set to allow the new collector device’s IP to query them with sufficient access?

You can use the Collector Update Scheduler to perform a one-time update to your LogicMonitor Collectors or to automate receipt of the most recent Collector updates at desired times.

Collector Release Tracks

Collector releases are categorized into three release tracks:

Early Access (EA) – EA releases are often the first to debut new functionality. We sometimes release a major feature in batches through EA release. So, EA is not recommended for your entire infrastructure. They occur 9-10 times per year. If there are major bug fixes, we patch EA, and it is referred as EA patch release. A stable EA version is designated as an optional general release (GD).
Optional General Releases (GD) – GD releases are stable collector updates that may have new features. However, it is not mandatory to update collectors with GD releases. They occur twice a year. If there are major bug fixes, we patch GD, and it is referred as GD patch release. A stable GD version is designated as Required General Release (MGD).
Required General Releases (MGD) – An MGD is released once a year. When we designate a GD as an MGD, we schedule and announce a date to auto-upgrade collectors to the MGD version. To let customers upgrade collectors as per their convenience, we send communication at least 30 days before the scheduled auto-upgrade date. On the auto-upgrade date, we upgrade only those collectors which are still below the MGD version. Thus, going forward, the MGD becomes the minimum required version. If there are major bug fixes, we patch MGD, and it is referred as MGD patch release.

Release Version Conventions

You can differentiate between an EA collector and a GD collector by observing the release version number.

All EA versions start with NN.100, where NN is the major version number. In subsequent releases, we increment the decimal. For example, EA 32.100, EA 32.200, and so on. In case of a patch to an EA, for example, patch to EA 33.100 is versioned as EA 33.101
All GD versions start with NN.000 where NN is the major version number. A GD release is followed by EA releases (usually 4-5 EA releases). So, in the subsequent releases, we increment the decimal. For example, after GD 32.000 is released, we will release EA 32.100, EA 32.200, EA 32.300, and so on. In case of a patch to a GD, the decimal number will always be below “.100”. For example, patch to GD 32.000 is versioned as GD 32.001
All MGD versions take the version number of the GD it is based on. For example, MGD 31.004 is based on the previously released GD 31.004

To understand collector releases and their versions, refer to the following example. Note that the version numbers are used for representation only.

Release Version	Details
EA 31.400	EA release
GD 32.000	GD release
EA 32.100	EA release
EA 32.200	EA release
GD 32.001	Patch to GD 32.000
GD 32.002	Patch to GD 32.001
EA 32.101	Patch to EA 32.100
EA 32.300	EA release
MGD 32.002	GD 32.002 is designated as the MGD
EA 32.400	EA release
GD 33.000	GD release

Collector Releases

For a summary of the key features included in each Collector version, see the following table. For a detailed description of what is included in each Collector release, view its dedicated version page.

Active Collector Releases

Version	Type	Release Date	JRE Version	Highlights
38.100	Early Access	June 24, 2025	jre_amazon_21.0.7.6.1	Watchdog Process Performance Improvement SBProxy Performance Improvement Migration to Amazon JAVA Corretto v21 See EA Collector – 38.100 for a complete list of enhancements and fixes.
38.000	Optional General Release	June 11, 2025	jre_amazon_11.0.27.6.1	Improvements to Watchdog Process Performance See GD Collector – 38.000 for a complete list of updates.
37.003	Optional General Release	June 10, 2025	jre_amazon_11.0.25.9.1	Fixed Linux Collector Upgrade Failure Issue See GD Collector – 37.003 for a complete list of updates.
37.300	Early Access	April 24, 2025	jre_amazon_11.0.26.4.1	Multiple Enhancements to Windows LogSource to Manage Log Ingestion and Filtering Support for OR Operator to Evaluate Filters in Syslog LogSource Support to run Windows_NonAdmin_Config.ps1 script in Domain Setup with Local User See EA Collector – 37.300 for a complete list of enhancements and fixes.
37.200	Early Access	March 13, 2025	jre_amazon_11.0.26.4.1	Support for Absolute Path in the MIBs to JSON Converter Utility New Timeout Configuration Added to Script Topology Tasks Updates to Chronicle Map Library See EA Collector – 37.200 for a complete list of enhancements and fixes.
37.002	Optional General Release	March 10, 2025	jre_amazon_11.0.25.9.1	Fixed Null Pointer Exception issue See GD Collector – 37.002 for a complete list of updates.
37.001	Optional General Release	February 19, 2025	jre_amazon_11.0.25.9.1	Improvements to WinRM See GD Collector – 37.001 for a complete list of updates.
37.100	Early Access	February 04, 2025	jre_amazon_11.0.25.9.1	Migration to Apache Groovy 4 Improvements to SNMP Trap as Logs Setting Non-admin User as the Default User for Windows Collector Installation Collector Debug Commands Security Update See EA Collector – 37.100 for a complete list of enhancements and fixes.
37.000	Optional General Release	January 27, 2025	jre_amazon_11.0.19.7.1	A potential fix to HostStatus alerts issue See GD Collector – 37.000 for a complete list of updates.
36.500	Early Access	December 19, 2024	jre_amazon_11.0.24.8.1	Updates to MongoDB Data Access Moving Linux Collector Services to User Service See EA Collector – 36.500 for a complete list of enhancements and fixes.
36.400	Early Access	November 06, 2024	jre_amazon_11.0.24.8.1	Addition of the collector performance analysis debug command Improvements to the custom size collector Updates to the default resource mapping list See EA Collector – 36.400 for a complete list of enhancements and fixes.
36.300	Early Access	October 03, 2024	jre_amazon_11.0.24.8.1	Improvements to the nonrootenhancements.sh file Improvements to the Ping Functionality Addition of Resource Property See EA Collector – 36.300 for a complete list of enhancements and fixes.
36.001	Optional General Release	September 04, 2024	jre_amazon_11.0.22.7.1	Improvements to collector live host reporting Support for processing and storing NBAR2 data asynchronously See GD Collector – 36.001 for a complete list of updates.
35.003	Required General Release	August 12, 2024	jre_amazon_11.0.19.7.1	MGD Collector 35.003 force update is scheduled on September 18, 2024. See MGD Collector – 35.003 for a complete list of enhancements.
36.200	Early Access	August 07, 2024	jre_amazon_11.0.23.9.1	Static Bearer Token Authentication Enabled for HTTPS Publisher New Wrapper Log Components for LogSource Flows See EA Collector – 36.200 for a complete list of enhancements and fixes.
36.100	Early Access	July 01, 2024	jre_amazon_11.0.23.9.1	Support for LogicMonitor Data Publisher Service with HTTPS client Support for BatchScript ConfigSource configuration Ingesting SNMP v1 and v2c traps without validation Access control for enhanced security See EA Collector – 36.100 for a complete list of enhancements and fixes.
36.000	Optional General Release	June 05, 2024	jre_amazon_11.0.22.7.1	Renamed the debug command to !winrm Implemented access control for enhanced security See GD Collector – 36.000 for a complete list of updates.

Archived Collector Releases

Version	Type	Release Date	Highlights
35.003	Optional General Release	July 02, 2024	jre_amazon_11.0.19.7.1 Fixed minor technical issue See GD Collector – 35.003 for a complete list of updates.
35.002	Optional General Release	June 03, 2024	jre_amazon_11.0.19.7.1 Renewed LMSignCert Fixed collector script cache issue See GD Collector – 35.002 for a complete list of updates.
35.401	Early Access	May 22, 2024	jre_amazon_11.0.22.7.1 Fixed minor technical issue See EA Collector – 35.401 for a complete list of enhancements and fixes.
35.400	Early Access	April 29, 2024	jre_amazon_11.0.22.7.1 Launched LogicMonitor Data Publisher Service Launched MIBs to JSON Converter Utility Auto Conversion of Linux Collectors to Non-root Users during Upgrade Renewed LMSignCert SNMP Trap Translation Improvements See EA Collector – 35.400 for a complete list of enhancements and fixes.
35.301	Early Access	March 12, 2024	jre_amazon_11.0.21.9.1 Fixed an issue where collector failed to ingest Syslogs due to 403 and 402 status codes See EA Collector – 35.301 for a complete list of enhancements and fixes.
35.300	Early Access	March 05, 2024	jre_amazon_11.0.21.9.1 You can now use the PowerShell script updateToNonAdmin.ps1 to migrate Windows collector running as admin to run as non-admin user Added matrices for monitoring ingestion of SNMP traps as LM Logs. Fixed an issue of missing logs. See EA Collector – 35.300 for a complete list of enhancements and fixes.
35.001	Optional General Release	February 13, 2024	jre_amazon_11.0.19.7.1 Fixed collector performance issue that occurred after upgrading to GD 35.000. Fixed an issue where the collector failed to downgrade from GD 35.000 and EA 35.200 to a previous version. See GD Collector – 35.001 for a complete list of updates.
35.200	Early Access	January 25, 2024	jre_amazon_11.0.21.9.1 Deprecated the Configure application in Windows collector. Added Regex group support to resource mapping for Syslog LogSource. Added the Enable for default log collection option on the Add Collector page. Fixed an issue related to Topology source feed parsing. See EA Collector – 35.200 for a complete list of enhancements and fixes.
35.100	Early Access	December 19, 2023	jre_amazon_11.0.21.9.1 Upgraded version of Amazon JAVA Corretto. Fixed minor security issues. SNMP Traps, Syslog, Windows Event Logging, and Script type LogSource now support the OR operator for resource mapping. See EA Collector – 35.100 for a complete list of enhancements and fixes.
35.000	Optional General Release	December 18, 2023	jre_amazon_11.0.19.7.1 Fixed security issue related to collector debug command and wrapper log. See GD Collector – 35.000 for a complete list of updates.
34.500	Early Access	November 01, 2023	jre_amazon_11.0.19.7.1 Collector now supports a new LogSource type ‘SNMP Trap’. In addition to Groovy lib v2, collector now also supports Groovy lib v4. Increased the scope of certain SNMP properties to be compatible with both SNMP v2c and v3. See EA Collector – 34.500 for a complete list of enhancements and fixes.
34.004	Optional General Release	October 16, 2023	jre_amazon_11.0.18.10.1 Fixed an issue where the script for PropertySources failed due to credential vault enhancements done in the previous release. See GD Collector – 34.004 for a complete list of updates.
33.007	Required General Release	October 06, 2023	jre_amazon_11.0.16.8.1 Fixed Linux collector upgrade issue. See MGD Collector – 33.007 for a complete list of enhancements and fixes.
34.400	Early Access	October 05, 2023	jre_amazon_11.0.19.7.1 Fixed an issue where the script for PropertySources failed due to vault enhancements done in the previous release. Stopped supporting the CSProxy feature in collector. Improved Delinea (previously Thycotic) Vault integration to fetch secrete values in multiple key-value pairs. See EA Collector – 34.400 for a complete list of enhancements and fixes.
34.003	Optional General Release	September 18, 2023	jre_amazon_11.0.18.10.1 The Selenium Synthetics Step Monitoring feature is added to GD Collector 34.003. See GD Collector – 34.003 for a complete list of updates.
34.300	Early Access	August 07, 2023	jre_amazon_11.0.19.7.1 Added max thread pool size parameter for Windows events and Syslog. Improved the Heap and Non-heap memory of small and medium size collectors for SNMP v2c. Upgraded version of some JAR files for minor security updates. See EA Collector – 34.300 for a complete list of enhancements and fixes.
34.002	Optional General Release	June 29, 2023	jre_amazon_11.0.18.10.1 Fixed collector upgrade issue that stopped working of the ping DataSource. Fixed collector upgrade issue that led to re-importing obsolete CAs in the upgraded JRE. See GD Collector – 34.002 for a complete list of fix.
34.200	Early Access	June 29, 2023	jre_amazon_11.0.19.7.1 Added reversal scripts to roll back WinRM configuration. Added Dynamic Regex Group method to SysLog LogSource field mapping. Fixed an issue where WMI query was run with empty credentials. See EA Collector – 34.200 for a complete list of enhancements and fixes.
34.001	Optional General Release	June 06, 2023	jre_amazon_11.0.18.10.1 Fixed issue that led to spike in SPSE and PowerShell task time out by reverting addition of host properties to hashtable/environmental variables. See GD Collector – 34.001 for details.
34.100	Early Access	June 01, 2023	jre_amazon_11.0.18.10.1 Introduced WinRM based solution to install Windows collectors without administrator privilege. Added a new module status for collector health check scripts. Separated credentials for SNMP traps and SNMP polling. See EA Collector – 34.100 for a complete list of enhancements and fixes.
33.401	Early Access	May 23, 2023	jre_amazon_11.0.18.10.1 Support to access the new Selenium Synthetics Step Monitoring feature. See EA Collector – 33.401 for details of the enhancement.
34.000	Optional General Release	May 17, 2023	jre_amazon_11.0.18.10.1 Fixed issue where collector crashed due to cache corruption in LiveHost. Upgraded Snippet JAR from version 1.5.3 to 1.8.2 See GD Collector – 34.000 for a complete list of fix.
33.400	Early Access	April 06, 2023	jre_amazon_11.0.18.10.1 Added Add additional SNMP v3 Credentials checkbox under Advanced NetScan for the ICMP ping method to provide multiple SNMP v3 credentials. Upgraded version of some files for various minor security updates. Added a new module status SignatureValueChangedForHealthCheckScripts for collector health check scripts. See EA Collector – 33.400 for a complete list of enhancements and fixes.
33.301	Early Access	March 06, 2023	jre_amazon_11.0.17.8.1 Fixed issues that led to high CPU spike and errors during data collection. See EA Collector – 33.301 for a complete list of enhancements and fixes.
33.300	Early Access	February 22, 2023	jre_amazon_11.0.17.8.1 Added the service.read_timeout_getconf property to the agent.conf setting. Upgraded version of some files for various minor security updates. See EA Collector – 33.300 for a complete list of enhancements and fixes.
33.200	Early Access	January 16, 2023	jre_amazon_11.0.17.8.1 Upgraded version of some files for various minor security updates. Fixed an issue where IPMI datasource and iDRAC monitoring could not collect data. See EA Collector – 33.200 for a complete list of enhancements and fixes.
33.101	Early Access	November 24, 2022	jre_amazon_11.0.16.8.1 Mitigated the risk of performance and availability impact on production Oracle environments by temporarily rolling back Oracle JDBC jar from version 21.5.0.0 to 11.2.0.3.0. See EA Collector – 33.101 for a complete list of enhancements and fixes.
33.100	Early Access	November 15, 2022	jre_amazon_11.0.16.8.1 Upgraded jsoup 1.14.2 to version 1.15.3 to mitigate vulnerabilities Added LogSource logging support in Collector for logsource.kubernetes and logsource.collectoringestapi components Introduced HostProps as an environment variable See EA Collector – 33.100 for a complete list of enhancements and fixes.
33.007	Optional General Release	September 04, 2023	Fixed issue related to Linux collector upgrade to GD Collector 33.006. See GD Collector – 33.007 for a complete list of fix.
33.006	Optional General Release	July 03, 2023	Fixed collector upgrade issue that led to re-importing obsolete CAs in the upgraded JRE. See GD Collector – 33.006 for a complete list of fix.
33.005	Optional General Release	June 06, 2023	Fixed issue that led to spike in SPSE and PowerShell task time out by reverting addition of host properties to hashtable/environmental variables. See GD Collector – 33.005 for details.
33.004	Optional General Release	May 02, 2023	Fixed issue where collector crashed due to cache corruption in LiveHost. See GD Collector – 33.004 for a complete list of fix.
33.003	Optional General Release	April 12, 2023	Fixed issues faced while upgrading collector from root to non root. Fixed issues related with ping DataSource and ping debug command. See GD Collector – 33.003 for a complete list of enhancements and fixes.
33.002	Optional General Release	February 20, 2023	Increased the thread count of collectors of different sizes. Fixed GD 33.001 upgrade related issues. See GD Collector – 33.002 for a complete list of enhancements and fixes.
33.001	Optional General Release	November 23, 2022	Mitigated the risk of performance and availability impact on production Oracle environments Upgraded some jar versions as part of minor security updates Fixed WMI password related issue See GD Collector – 33.001 for a complete list of enhancements and fixes.
33.000	Optional General Release	November 10, 2022	Fixed WMI password related security issue Upgraded hsqldb jar to version 2.7.1 See GD Collector – 33.000 for a complete list of enhancements and fixes.
32.004	Optional General Release	November 01, 2022	Fixed wmi password related security issue. See GD Collector – 32.004 for a complete list of enhancements and fixes.
32.400	Early Access	September 22, 2022	Upgraded Corretto JRE version to 11.0.16.8.1 Discontinued the support for jt400-full-6.0.jar (IBM iSeries/AS400 JAR) Improved the Enhanced Script NetScan feature See EA Collector – 32.400 for a complete list of enhancements and fixes.
32.003	Optional General Release	September 20, 2022	Applied a fix that resolves the null pointer exception when upgrading Collector. See GD Collector – 32.003 for details.
31.004	Required General Release	August 30, 2022	Upgraded log4j to version 2.17.1 to mitigate the log4j vulnerabilities. Upgraded Fastjson to version 1.2.83 to mitigate the Fastjson “Auto Type Bypass” CVE-2022-25845 RCE vulnerability. See MGD Collector – 31.004 for a complete list of enhancements and fixes.
32.002	Optional General Release	August 29, 2022	Upgrade to Postgresql version 42.4.1 to mitigate CVE-2022-31197 security vulnerability in the JDBC jar file for postgres. Patch to a fixed issue where Collector took more time to upgrade resulting in Collector down alert. See GD Collector – 32.002 for a complete list of enhancements and fixes.
32.300	Early Access	August 9, 2022	Improved Advance NetScan by adding a new Enhanced Script NetScan method. Upgraded fastjson to version 1.2.83 to mitigate CVE-2022-25845 vulnerability. Made changes to support systemd/system as the default Daemon directory to support the CentOS Stream versions. See EA Collector – 32.300 for a complete list of enhancements and fixes.
32.001	Optional General Release	June 29, 2022	To mitigate the Fastjson “Auto Type Bypass” CVE-2022-25845 RCE vulnerability, we have upgraded Fastjson to version 1.2.83. See GD Collector – 32.001 for a complete list of enhancements and fixes.
31.004	Optional General Release	June 29, 2022	To mitigate the Fastjson “Auto Type Bypass” CVE-2022-25845 RCE vulnerability, we have upgraded Fastjson to version 1.2.83. See GD Collector – 31.004 for a complete list of enhancements and fixes.
32.200	Early Access	June 27, 2022	In addition to CyberArk single account, we have now extended support to CyberArk dual account. LogicMonitor now automates the OSS license report generation process. To mitigate the Fastjson “Auto Type Bypass” CVE-2022-25845 RCE vulnerability, we have upgraded Fastjson to version 1.2.83. See EA Collector – 32.200 for a complete list of enhancements and fixes.
32.100	Early Access	June 03, 2022	Added a new toggle on the Netscan UI. Configure Netscan policies individually to include or exclude network and broadcast addresses when scanning CIDR ranges. See EA Collector – 32.100 for a complete list of enhancements and fixes.
32.000	Optional General Release	June 03, 2022	LogicMonitor Collector now monitors and identifies changes in the jar files shipped during the Collector installation. Changes are highlighted on the Collector status page. Added new Netflow configurations. See GD Collector – 32.000 for a complete list of enhancements and fixes.
31.200	Early Access	March 31, 2022	Added and updated Netflow configurations. Upgraded Amazon Java Corretto to version 11.0.14.10.1. Added new properties to the JDBC data collection settings in the agent.conf file. See EA Collector – 31.200 for a complete list of enhancements and fixes.
31.100	Early Access	February 17, 2022	Added support for three new LogicModules: Windows Events Logs Collection, Kubernetes Events, and Kubernetes Pod Logs. Added the ability to select more than one label for instance definitions in the OpenMetrics wizard. See EA Collector – 31.100 for a complete list of enhancements and fixes.
30.003	Optional General Release	February 17, 2022	Upgraded log4j to version 2.17.1 to mitigate the log4j vulnerabilities. See GD Collector – 30.003 for a complete list of enhancements and fixes.
31.003	Optional General Release	January 17, 2022	Upgraded log4j to version 2.17.1 to mitigate the log4j vulnerabilities. See GD Collector – 31.003 for a complete list of enhancements and fixes.
31.002	Optional General Release	December 21, 2021	Upgraded log4j to version 2.17 to mitigate the log4j vulnerabilities. See GD Collector – 31.002 for a complete list of enhancements and fixes.
30.002	Required General Release	December 17, 2021	Upgraded log4j to version 2.16 to mitigate the Log4shell vulnerabilities. See MGD Collector – 30.002 for a complete list of enhancements and fixes.
31.001	Optional General Release	December 16, 2021	Upgraded log4j to version 2.16 to mitigate the Log4shell vulnerabilities. See GD Collector – 31.001 for a complete list of enhancements and fixes.
31.000	Optional General Release	November 26, 2021	Includes all features and fixes from the EA Collector 30.xxx versions Updated Java to Amazon Corretto 11.0.13.8. See GD Collector – 31.000 for a complete list of enhancements and fixes.
30.104	Early Access	October 19, 2021	Certified the Collector to run on RHEL OpenShift. Added TCP support for Syslog log collection. Added performance enhancements to the OpenMetrics Collector. See EA Collector – 30.104 for a complete list of enhancements and fixes.
30.001	Optional General Releases	August 23, 2021	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 See GD Collector – 30.001 for a complete list of enhancements and fixes.
30.102	Early Access	July 20, 2021	Added Beta Support for the new Thycotic Secret Server as part of the Credential Vault Integration. Added the functionality to change the Collector Size setting during installation. See EA Collector – 30.102 for a complete list of enhancements and fixes.
30.101	Early Access	June 9, 2021	Added support for High Security mode (HSM). Users can choose to install in HSM or Orchestration Compatibility Mode (OCM). The default is OCM. Added functionality to override openmetrics.url property with openmetrics.host or system.hostname properties when the URL isn’t provided. See EA Collector – 30.101 for a complete list of enhancements and fixes.
30.000	Optional General Releases	April 29, 2021	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). See GD Collector – 30.000 for a complete list of enhancements and fixes.
30.100	Early Access	April 20, 2021	Added support for new OpenMetrics collection. Added support for Windows Events Logs and Kubernetes Events collection and forwarding to LM Logs Added JMX metrics for monitoring the CyberArk AAM Credential Vault integration. See EA Collector – 30.100 for a complete list of enhancements and fixes.
29.109	Early Access	March 30, 2021	Fixed an issue in EA 29.107 where upgrading failed if the Collector is running as root. See EA Collector – 29.109 for a complete list of enhancements and fixes.
29.108	Early Access	March 11, 2021	Added integration support for external credential management using CyberArk Vault. See EA Collector – 29.108 for a complete list of enhancements and fixes.
29.107	Early Access	March 9, 2021	See EA Collector – 29.107 for a complete list of enhancements and fixes.
29.106	Early Access	February 10, 2021	Fixes the known issue present in versions 29.101 through 29.105 that was resulting in resources with heartbeats to be incorrectly marked as dead/down. Updated to no longer require changes to /etc/sudoers for non-root installation. JMX metrics added for LM Logs. See EA Collector – 29.106 for a complete list of enhancements and fixes.
29.105	Early Access	December 9, 2020	Adds support for parsing RFC 3164 and RFC 5424 formatted log events. Introduces several new properties for tuning Web Checks. See EA Collector – 29.105 for a complete list of enhancements and fixes.
29.104	Early Acess	October 10, 2020	Support for forwarding syslog to LM Logs. See Collecting and Forwarding Syslog Logs. Upgraded Amazon Java Corretto to 11.0.9.11.1 (October 2020 quarterly update). Support for the Suppress duplicate EventIDs even when messages differ option has been added. See EA Collector – 29.104 for a complete list of enhancements and fixes.
29.003	Optional General Releases	September 29, 2020	Upgraded the JRE to Amazon Corretto 11.0.8.10.1 See GD Collector – 29.003 for a complete list of enhancements and fixes.
29.102	Early Access	September 15, 2020	Adjusted the output text width of Collector debug information, making Java exception text easier to read. Removed several Java libraries from the Collector. See EA Collector – 29.102 for a complete list of enhancements and fixes.
29.002	Optional General Releases	August 17, 2020	Fixes an issue causing web page collection tasks to get held up and consume CPU.
29.101	Early Access	August 6, 2020	Upgraded the JDK to Amazon Corretto 11.0.8.10.1. NetScan Groovy scripts are now run in the SSE. NBAR slots support for Direction, IPv6, Application. See EA Collector – 29.101 for a complete list of enhancements and fixes.
29.001	Optional General Releases	July 15, 2020	Collector version GD 29.001 fixes an issue in GD 29.000 that prevented the successful upgrade to GD 29.000 from an EA 28 version (28.400 – 28.607) of a Linux Collector running as a non-root user.
29.000	Optional General Releases	July 6, 2020	Collector version GD 29.000 incorporates all enhancements and fixes found in M/GD 28.005, as well as EA 28.xxx (28.100, 28.200, 28.300, 28.400, 28.500, 28.501, 28.600, 28.601, 28.602, 28.603, 28.604, 28.605, 28.606, 28.607). Visit the individual release notes pages for more information.
29.100	Early Access	June 24, 2020	Introduces XL and XXL size collectors for 16 and 32 GiB of RAM. Introduces the Collector Script Cache to allow caching of things like session tokens between collection intervals, without dumping things on the filesystem. Added scripts to allow the migration of a Collector running as root or Administrator to a non-root or non-Administrator user. TinyRADIUS Java Library is now included. LogicModules that utilize these to test RADIUS login will be available in a future release. See EA Collector – 29.100 for a complete list of enhancements and fixes.
28.607	Early Access	May 27, 2020	Enhancements: Updated the Collector JRE to Amazon Corretto version 11.0.7.10 (April 2020 patch) Fixes: Fixed an issue where AES-256 SNMPv3 was not working with some Cisco devices
28.606	Early Access	May 7, 2020	Improvements: Added SHA2 support for SNMPv3 Added SSHJ library as an option for Expect. This includes more ciphers, algorithms, and key exchanges, including the 4096 bit Diffie-Hellman group Updated MariaDB driver to mariadb-java-client-2.5.4.jar Improved logging for remote sessions Fixes: Fixed issue in the Linux installer that was preventing the Collector from starting when installed as non-root on some machines
28.005	Required General Releases	May 5, 2020	Improvements: PropertySource support for token replacement in PowerShell scripts Support for NTLMv2 authentication via the `wmi.authType` property More insightful error messages and diagnosis when using the Poll Now functionality Remote Session support via Collectors configured to use proxies Improved metrics for SSE and Collector performance monitoring Collector logging cleanup Topology mapping support Fixes: Accurate parsing of Cisco syslog messages lacking a host for Syslog EventSources SSL validation issue fix that was preventing successful Groovy script execution
28.605	Early Access	March 19, 2020	Improvements: Upgraded the MS SQL jar to mssql-jdbc-7.4.1.jre11.jar Improved memory usage on the syslog Collector Added a log event for when the SSE fails to start Internal improvements to the Collector reporting mechanism Fixes: Fixed message parsing issue that was preventing the ##MESSAGE## token from rendering appropriate contents when a Windows event was generated
28.604	Early Access	January 8, 2020	Improvements: Updated the JDK to Amazon Corretto 11.0.5.10.1 (October 2019 Critical Patch Update). Fixes: Fixed NetFlow aggregation edge case with invalid port “0” would cause display issues in the Traffic tab. Fixed issue introduced in 28.003 that would break Batchscript collection if the instance identifier contained a “.” Fixed issue that would cause Ping check to errantly return status 24 in edge cases.
28.004	Optional General Releases	October 25, 2019	Fixes: Fixed issue introduced in 28.003 that would break Batchscript collection if the instance identifier contained a “.”
28.003	Optional General Releases	October 15, 2019	Improvements: Improved performance for Batchscript DataSources with very large numbers of instances. Fixes: Fixed issue that would cause Ping check to errantly return status 24 in edge cases. Backported from EA 28.500
28.603	Early Access	September 5, 2019	Improvements: Updated the Corretto JRE to 11.0.4
28.602	Early Access	August 8, 2019	Fixes: Fixed a bug that would cause JDBC Active Discovery to ignore the “Port # List” field.
28.601	Early Access	July 24, 2019	Fixes: Fixed issue with watchdog that would prevent the collector configuration from being edited in the UI NOTE: If you’re upgrading from 28.600, the watchdog issue above will prevent a normal upgrade. There are two options to workaround the watchdog bug to update to 28.601: Uninstall the collector from its host, download collector 28.601 from the portal (you don’t need to delete or recreate the collector object in LogicMonitor) and install it on the host. Open the collector debug window and run the !restart command to restart the collector. This will temporarily fix the environment (until the next automated collector credential rotation) and allow you to upgrade via the portal. Restarting the collector via the drop-down UI menu won’t work for the workaround, it must be the debug command
28.600	Early Access	July 5, 2019	Fixes: Fixed issue with Collector signing that could: Cause false positives from anti-virus software Block collection and reporting tasks
28.501	Early Access	June 21, 2019	Fixes: Fixed issue with Collector signing that could: Cause false positives from anti-virus software Block collection and reporting tasks
28.500	Early Access	June 14, 2019	Improvements: Collector installer now uses Bash and interfaces with systemd. If you download 28.500 on v120 it will still use Perl. !logsurf debug command will now show details for Test Script. PIDs are now logged for troubleshooting external scripts. Fixes: Fixed bug that broke SNMP collection when two resources have the same IP address and different host names. Avoid potential false No Data reported for Ping data collection when restarting Collector. Fixed issue that would cause some NetFlow v9 data to be discarded in some circumstances. Fixed issue that would cause Ping check to errantly return status 24 in edge cases. Fixed a memory leak in the syslog collector. Fixed bug that would cause JDBC collection to fail if special characters were in the URL.
28.400	Early Access	May 23, 2019	Improvements: Added support for Test EventSource (SNMP trap, syslog, logfile) functionality Collector now runs on Amazon’s Corretto JDK 11 Notes: With this change, we’ve dropped support for 32-bit operating systems At least initially, this will incur a roughly 10% increase in CPU and memory usage. We’re working to reduce this in future versions. !logsurf debug command now provides additional log context from sbproxy.log (for WMI, Perfmon, and Ping tasks) Improved PropertySource scheduling to avoid CPU spikes The installer on Windows now confirms a successful install to avoid silent failure Improved NetFlow performance by removing extraneous logging Upgraded AWS SDK from 1.11.431 to 1.11.548 Fixes: Fixed !tplist “STATUS” field that would show OK despite there being an error
28.300	Early Access	May 7, 2019	Improvements: Better monitoring of overall memory and CPU usage via a new Collector DataSource. Reduce collector memory usage for Active Discovery history. Linux collector will create a non-privileged logicmonitor user to run the collector when non-root is selected. Support for running system’s snmpwalk and snmpget commands (useSystem=true) Reduced SSE memory usage for Internal Web Checks Improved WMI error handling logic to avoid gaps and return the real error code in more cases Test Active Discovery for SNMP now returns diagnosis commands for both getNext and getBulk Improve JMX data collection logic to avoid potential data gaps when invalid connections were errantly cached Improved the uninstaller to completely remove the Collector in some scenarios where it was only partially uninstalled Fixes: Fixed potential memory leak with the ESX collector Fixed an issue where the Windows Collector device name was shown incorrectly as “Unknown” Fixed issue where syslog collector used excessive memory Fixed the error that created a useless folder in the install directory
28.200	Early Access	April 10, 2019	Improvements: Reduced memory usage for PropertySources CPU usage optimizations Improved instance names on SSE Datasources Improved NetFlow diagnosis messaging Improved Windows EventLog query time range processing to avoid fails queries Changed pdh.auto.switch.to.native.enable to default to true. Also fixed an issue where Perfmon collection would fail when pdh.datacache.enableand pdh.auto.switch.to.native.enable were both set to true JMX collection now supports the special character “:” in MBeans Fixes: Fixed batchscript collection caching behavior that would cause some instances with duplicate wildvalues to report No Data Fixed password exposure issue with Poll Now Diagnosis for WMI Fixed issue where NetFlow would record corrupt data instead of discarding it Fixed an issue where JobMonitors would alert unexpectedly due to slight clock skew. If the reported time of the job (from the wrapper script) is more than a minute different from Santaba time, we’ll use Santaba time Fixed a condition that could potentially hang the Watchdog and prevent Collector upgrades
28.002	Optional General Releases	April 2, 2019	Fixes: Fixed batchscript collection caching behavior that would cause some instances with duplicate wildvalues to report No Data. Fixed password exposure issue with Poll Now Diagnosis for WMI.
28.001	Optional General Releases	March 21, 2019	Fixes: Fixed issue where JDBC AD and Collection would fail if the domain name contains “-“. Fixed memory leak issue with Groovy tasks.
28.100	Early Access	March 20, 2019	Improvements: The collector can now run without administrative or root privileges on both Windows and Linux. Administrator/root privileges are still needed for the initial installation. Syslog performance has been improved. Modifications to the JRE keystore are now kept during collector upgrade. Fixes: Fixed InstallShield Wizard progress bar which didn’t fill, causing unnecessary uncertainty about the process. NetScan will not use ARP to scan hosts outside of the same subnet. This lead to incorrect device types being reported. Fixed a possible memory leak when using SNMPv3. Fixed issue where Ping task would non report data if it timed out. Fixed issue where JDBC AD and Collection would fail if the domain name contains “-“. Fixed memory leak issue with Groovy tasks.
28.000	Optional General Releases	February 27, 2019	GD Collector 28.000 will be available February 27th, 2019. This version includes everything in GD 27.001, GD 27.002, GD 27.003, GD 27.004, GD 27.005, as well as EA 27.100, EA 27.200, EA 27.300, EA 27.400, EA 27.500, EA 27.600, EA 27.700, EA 27.750, EA 27.751, EA 27.800, EA 27.850, EA 27.900. In comparison to GD 27.001, highlights of this version include: Property Sources now support token replacement inside Powershell Scripts Added support for NTLMv2 authentication using wmi.authType More insightful Poll Now error messages and diagnosis Remote Sessions are now supported through a collector configured to use a proxy Improved metrics for SSE and Collector performance monitoring Syslog EventSources now correctly parse Cisco syslog messages lacking a host Cleaned up collector logging Fixed an issue where SSL validation prevented Groovy scripts from running successfully For more detailed information on what’s included, see individual EA release notes (links above).
27.900	Early Access	February 21, 2019	Improve Windows Event Log performance in some scenarios Improve AD task duplication logic. Previously, this could result in delayed AD results, which would make AD appear to be broken. Improved AD memory usage Reduced CPU usage for SNMP v3 collection Added hostactive column to !tlist output. When “true”, successful tasks will contribute to the “heartbeat” (see HostStatus DataSource) that signals that the device is alive (or dead in its absence). When “false”, it means the tasks success has no impact on the heartbeat or the collector’s up/down status. Avoid false host down alerts when sbproxy is unexpectedly down.
27.850	Early Access	January 23, 2019	Improve Windows Event Log performance in some scenarios Improve AD task duplication logic. Previously, this could result in delayed AD results, which would make AD appear to be broken. Improved AD memory usage Reduced CPU usage for SNMP v3 collection Added hostactive column to !tlist output. When “true”, successful tasks will contribute to the “heartbeat” (see HostStatus DataSource) that signals that the device is alive (or dead in its absence). When “false”, it means the tasks success has no impact on the heartbeat or the collector’s up/down status. Avoid false host down alerts when sbproxy is unexpectedly down.
27.800	Early Access	January 3, 2019	Improved SNMP Poll Now diagnosis messages. Improved Poll Now error messages when running external/uploaded scripts. During upgrade, collector will report any processes it can’t kill that it must kill to upgrade. Installer will warn if collector user lacks required permissions. Various improvements to collector logging. Better -help output for !tlist debug command. Handle SNMP agents that return “noSuchName” in the “error-status” field. Default configuration changes to watchdog.conf: wrapper.logfile.compress.maxfiles changed from 10 to 5 wrapper.logfile.maxfiles changed from 3 to 2 Default configuration changes to wrapper.conf: wrapper.logfile.compress.maxfiles changed from 10 to 20 wrapper.logfile.maxfiles changed from 3 to 2 The following configuration directives have been renamed: discover.global.timeoutInSec -> discover.default.timeoutInSec (default 3600) discover.perfmon.timeout -> discover.perfmon.timeoutInSec (default 120) discover.wmi.timeout -> discover.wmi.timeoutInSec (default 120) Added AD script timeout configuration directive discover.script.timeoutInSec with a default value of 300 seconds. Fixed issue where sbwinproxy would use more memory than necessary when communication to the agent was interrupted. Fixed an issue where a PowerShell script would report “The screen cannot be set to the number of lines and columns specified.” when run from Poll Now or the debug window. This happened because the collector tried to set the screen column count to the default value despite it already being set to the default value. Fixed a bug where WMI queries would fail due to an improperly handled error code that requires re-authentication. Fixed issue where ping collection would fail with some firewalls due to sequence ID reuse.
27.751	Early Access	December 25, 2018	Fixed a bug that would cause some collectors to use excessive memory and CPU for garbage collection when monitoring single devices with more than 10,000 instances that are frequently changing.
27.005	Required General Releases	December 5, 2018	Since 25.200, nonexistent OIDs in AD filters would cause an instance to be filtered out of AD unless the filter was using the NotExist operation. This would lead to unexpected behavior when using other operations like NotEqual, NotContains, and RegexNotMatch. Nonexistent OID responses will now be treated as empty strings (“”) when evaluating with those operations. Token replacement for PropertySources now works in Groovy and PowerShell. We recommend using hostProps.get(), instanceProps.get(), or taskProps.get() in Groovy scripts for better performance than token replacement. Collector will no longer fail to start if DNS resolution from the cache file fails. Fixed issue where sbwinproxy would use more memory than necessary when communication to the agent was interrupted.
27.750	Early Access	November 22, 2018	HTTP collector AD will not append default ports (80, 443) to the “Host” header. Most browsers, and the !http debug command did not append the port to the “Host” header, leading to discrepancies in cases where the remote server could not handle the appended port in the “Host” header. Syslog collection now supports timestamps with microseconds. The collector will delete the locally stored NetFlow database if the file exceeds netflow.datadir.maxSizeInMB directive in agent.conf when NetFlow initializes. This will prevent NetFlow from using excessive collector disk space. When Poll Now fails for Ping, SNMP, or WMI collection, the collector will try to diagnose the problem and include suggestions (as well as the command used to diagnose) in the result. Ping diagnosis calls your collector OS ping binary. SNMP diagnosis uses binaries included with the collector. WMI diagnosis uses PowerShell’s Get-WMIObject Cmdlet. Fixed handling of gzip encoding with the webpage collector. Patched CVE-2016-5725 on JSch 0.1.53.
27.700	Early Access	November 2, 2018	Improved memory efficiency for WMI, Perfmon, and Ping collection. Unused .cab files generated with the !packetcapture debug command are now automatically deleted. Memory usage improvements. Various improvements to logging output. Improved SSE memory usage when consuming the hosts feed, particularly for collectors handling large numbers of instances. Fixed issue where Perfmon collection could interfere with the watchdog heartbeat, resulting in errant host status alerts.
27.004	Optional General Releases	November 1, 2018	SSE will be automatically disabled on collectors that can’t support it due to insufficient RAM and other edge cases. Improved memory efficiency for WMI, Perfmon, and Ping collection. Improved SSE memory usage when consuming the hosts feed, particularly for collectors handling large numbers of instances. Various stability improvements. Reverted JSch library to 0.1.53 from 0.1.54 to fix a compatibility issue with some Cisco devices. Fixed issue where sbproxy would be errantly terminated.
27.600	Early Access	October 15, 2018	Syslog EventSources now recognize and correctly parse Cisco’s flavor of syslog. Efficiency improvements to the built-in NetApp collector. Trimmed down some excessively long collector event messages. Efficiency improvements for PowerShell scripts. More insightful error messages from Poll Now. NetScan script timeout is now configurable in agent.conf (defaults to 60 seconds). Fixed issue where sbproxy would not restart timely when a collector was restarted from the UI. Fixed issue where sbproxy would be errantly terminated. Fixed a NetFlow bug that would cause data to be discarded if the device id was too large. Fixed an issue that prevented PowerShell scripts from running after upgrading to 27.500.
27.500	Early Access	September 13, 2018	Includes all fixes in 27.003, Plus: Added an option to use unique ids per host on icmp polls. Improved metrics for SSE and Collector performance monitoring. Fixed an issue where restarting with a corrupted agentdns.cache file would prevent collector from starting.
27.003	Optional General Releases	September 13, 2018	The SSE engine now supports custom lib folders, including relevant paths, for 3rd party jars. Added an option to execute parallel perfmon metric collection for situations where some parent metrics might be invalid. Added additional status monitoring of the Collector Reporter to identify situations where the Collector may be reporting data, but no gathering fully. Fixed a bug where the Collector was being repeatedly restarted by improving the logic that Watchdog uses to restart the collector agent. Fixed a bug in SNMP collection when gathering metrics individually which resulted in “ConcurrentModificationException” errors. Fixed a bug where certain Groovy Scripts would not work and display this error “Cannot schedule task for execution” after disabling the Standalone Scripting Engine. Fixed a bug where “reporter.persistent.queue.consume.rate” config setting was not being used. Fixed a bug where very large host entries would cause an OutOfMemory exception. The script will be scheduled for later execution or SSE will be disabled until next restart when the process does not register within a configured initiation time. Fixed a resource leak in Standalone Scripting Engine and added increased protection for OutOfMemory exceptions and SSE spawning too many processes. Increased security to prevent DLL hijacking in sbwinproxy.
27.400	Early Access	August 17, 2018	Remote Sessions are now supported through a collector configured to use a proxy. Improved PollNow Error messages for Ping and Perfmon datasources to help with troubleshooting.
27.300	Early Access	July 25, 2018	Added ability to specify as specific MySQL JDBC driver jar over the currently provided version. Webpage collection of JSON data is now cached locally to improve performance of reading large data sets. Fixed an issue where TCP Connections were not being reused correctly and creating significantly more open connections than previous versions.
27.002	Optional General Releases	July 25, 2018	Fixed an issue where SSL Certs validation was preventing certain Groovy Scripts from successfully running. Fixed an issue with the Watchdog process frequently restarting SBProxy process. Fixed an issue where upgrading from 26.XXX to 27.XXX resulted in more variability in Data Collection Task counts. The timeout value for collector.max.init.delay.in.seconds is now defaulted to 600. Fixed an issue when perfmon initialization against a slow endpoint may cause a restart of the sbproxy service.
27.200	Early Access	July 10, 2018	Improved the memory handing of Powershell scripts. Poll Now on JDBC datasources now provides more detailed error messages.
27.001	Optional General Releases	July 10, 2018	Fixed an issue with JDBC data collection and making TLS connections. SBWinProxy was restarting randomly and impacting the ability to monitor Ping DataSources. Improved the default Memory Allocation around the scripting environment. When proxy.enable=true in agent.conf, the collector will check the proxy certificate for validity. The collector will not connect to Santaba if the certificate fails the validity check.
27.100	Early Access	June 13, 2018	PropertySources written in PowerShell now support token replacement. Added support for NTLMv2 authentication using wmi.authType.
27.000	Optional General Releases	June 12, 2018	GD Collector 27.000 will be available June 12, 2018. This version includes everything in GD 26.001, as well as EA 26.100, EA 26.200, EA 26.201, EA 26.300, EA 26.400, EA 26.500, EA 26.600 and 26.601. In comparison to GD 26.001, highlights of this version include: Property Sources now support Powershell Scripts Removed Support for Windows 2003 Windows Collector installer and files are now signed Support for Event Source Test Now functionality (similar to Poll Now on datasources)
26.601	Early Access	May 29, 2018	We highly encourage everyone using EA Collectors 26.100 – 26.600 to upgrade to this version. This version will become our next Optional General Releases Collector. This release includes the following: Fixed an installation issue on Windows 2008 R2 where the installer was asking for Proxy information due to connection issues. Fixed a data collection issue related to specific special characters included in SQL statements.
26.600	Early Access	May 17, 2018	Fixed an issue with SNMP v3 collection that would result in very high CPU usage. Fixed “WMI Provider load failure” issue. Fixed an issue where certain collector upgrade paths would not maintain/adjust Agent.conf file customizations properly.
26.500	Early Access	April 12, 2018	Support for Event Source Test Now functionality (similar to Poll Now on datasources) that is coming in v103. Configuration updates/changes to support the renaming of Services to Websites. Added support for integers with 5 bytes in SNMP.
26.400	Early Access	March 22, 2018	Support for Longer DataSource Collection Intervals. A new property “collector.script.timeout” can be set on an instance, device or group and we use that property value as any script timeouts for instances where the property is applied. We have improved the handling of reporting threads to ensure that collectors with high device counts process tasks more efficiently during heavier loads
26.300	Early Access	March 4, 2018	Groovy Scripting will now support PUT and DELETE methods as part of an updated HTTP java class. Support for the upcoming Log File Event Source Encoding options that allow for choosing or auto-detecting the encoding of collected log sources. Support for the upcoming Powershell support in Property Sources.
26.201	Early Access	January 29, 2018	Fixed a bug in the Internal Service Check to better support SSL checks on alternative port numbers.
26.200	Early Access	January 26, 2018	Support for the upcoming v101 release feature enhancement Property Sources will support PowerShell scripts. With this version of the collector Windows 2003 is no longer supported and will be blocked by installation and upgrades. Service Checks now support the ability to identify SSL errors and halt on them as separate actions. Therefore the check can identify the SSL error, but continue to confirm the rest of the service functionality. Use 26.200 to use this feature with Internal Service Checks.
26.001	Optional General Releases	January 23, 2018	GD 26.001 fixes an issue identified in GD 26.000 that could affect LogicMonitor performance. If you are running 26.000, please update to this new 26.001 version.
26.100	Early Access	January 16, 2018	Improved stability of scripted Data Collection and Active Discovery. With v100, Windows Collector installers will be signed for enhanced security. Previously, if the Collector requested ESX data during a refresh of the ESX server, it would report “No Data” until the Collector was restarted. This has been improved so that the Collector can recover without requiring a restart. Added support for TLS 1.1/1.2 for MySQL and SQL Server.
26.0	Optional General Releases	January 4, 2018	This version includes everything in GD 25.001, as well as EA 25.100, EA 25.200, EA 25.300, and EA 25.400. Improved speed and performance of NetScans. Support for SSL Expiration tracking and alerting for Service Checks. Support for groovy scripts to define a Config Check in LM ConfigSources
25.400	Early Access	December 18, 2017	Improved WMI performance and capacity. Improved Active Discovery and Auto-Property processes to prevent duplicate tasks and reduce memory usage. Increased the timeout of SNMP Active Discovery tasks to 300 seconds. This can be modified via the ad.snmp.walk.timeout parameter in agent.conf Improved snmpwalk timeout logic.
25.300	Early Access	November 9, 2017	Significant performance improvements for Perfmon collection. Performance and capacity improvements for WMI collection. Windows Collector Installer has been improved to better explain permissions/installation instructions. It will now automatically detect if the computer is on the domain and show a separate Domain field only in this case. Support for SSL expiration monitoring in v97.
25.001	Optional General Releases	October 25, 2017	GD 25.001 will be released October 25th, 2017 to replace GD 25.000, which was released early September. We have subsequently identified an issue in GD 25.000 that could cause problems with PowerShell script execution under certain conditions. With GD 25.000, we improved the ability of the Collector to trap PowerShell exceptions, and it is possible this would terminate PowerShell script execution for otherwise harmless errors. We have corrected and thoroughly tested this in GD 25.001.
25.200	Early Access	October 19, 2017	Improved the speed and performance of NetScan. Added Npcap packet capture for MAC address detection and lookup of network interface manufacturer. You can now use groovy scripts to define a Config Check in LM ConfigSources. To avoid ping packages from being dropped by firewalls, we have reduced the Collector’s default ping packet size. To change this, you can modify the ‘ping.payload.size’ parameter in the Collector’s service.conf file Removed the !get debug command.
25.0	Optional General Releases	September 8, 2017	This version includes everything in MGD 24.002, as well as EA 24.085, EA 24.126, EA 24.200, and EA 24.300. Easy Capacity Tuning – Navigate to the Collector configuration window and select a new Collector size (Small, Medium, or Large) to automatically update the necessary parameters and instantly increase or decrease the Collector’s capacity. Support for IPv6 for all data collection methods and Internal Service checks (not including traceroute, yet). Faster Collector download – When adding a Collector, select ‘bootstrap’ to download and install Collectors much faster via the LogicMonitor CDN.
24.300	Early Access	August 25, 2017	Faster Collector download! When adding a Collector version 24.300 or higher with v94, you will notice the option to download a bootstrap as opposed to the full Collector package. The bootstrap is a smaller installation package that enables you to download and install Collectors much faster via the LogicMonitor CDN. Added a service.config tab to the Collector Configuration window. This is useful for configuring a proxy and other settings for Internal Service checks. SNMP performance improvements to reduce the Collector’s CPU utilization. Reduced the amount of memory used by ConfigSources.
24.126	Early Access	July 14, 2017	This version supports one click capacity optimization. You can now navigate to the Collector configuration window and select a new Collector size (Small, Medium, or Large) from a dropdown menu. Added a sanity check to any configuration changes made via the UI Several improvements to support IPv6 for all data collection methods. Added the ability to configure a proxy for Internal Service checks. This configuration is set in the Collector’s service.conf file
24.002	Required General Releases	June 29, 2017	This Collector includes all features available in 24.001 as well as the following changes: Improved the logic behind the Collector upgrade process to ensure that custom script and jar files are not inadvertently deleted during upgrade. Fixed an issue causing double backslashes to be interpreted incorrectly in Powershell scripts. Improved DNS resolve to prevent service checks from failing due to containing “://”

Overview

When you delete a Collector from your LogicMonitor account, the Collector and Watchdog services should stop and the Collector should uninstall itself. If your Collector does not correctly uninstall itself, you can manually stop the Collector and Watchdog services and uninstall the Collector from the device.

Removing the Collector from Your Account

Re-assign the devices being monitored by that Collector to a different Collector – you can re-assign devices in bulk by selecting the devices icon for the Collector you’d like to remove.
Select Delete for the Collector:

Manually Removing the Collector from a host Resource

In some cases you might need to manually stop the Collector services and then remove/uninstall the Collector from your host resource.

Windows

Navigate to the services control panel for your Windows machine and stop the ‘LogicMonitor Collector’ and ‘LogicMonitor Collector Watchdog’ services. You can then uninstall the Collector using the standard Windows ‘Add or remove programs’ controls.

Linux

Navigate to [LogicMonitor Collector Directory]/agent/bin and execute the sbshutdown script to shut down both the Collector and Collector Watchdog services. For example:

# cd /usr/local/logicmonitor/agent/bin
# ./sbshutdown

Then you can uninstall the Collector by calling:

# ./uninstall.sh

Alternatively, you could do a recursive removal of the logicmonitor Collector directory and all its contents (there are symbolic links in /etc/init.d for logicmonitor.collector and logicmonitor.watchdog, and those should be removed to ensure the services do not keep running in memory). For example:

# rm -rf /usr/local/logicmonitor

Overview

The LogicMonitor Collector is the heart of your monitoring system. As such, it’s important that you monitor your Collectors to ensure that performance is keeping up with data collection load. Equally important is ensuring the least disruption possible when a Collector does go down. This includes making sure timely notifications are delivered to the appropriate recipient(s).

As best practice, LogicMonitor recommends that you (1) set up monitoring for your Collectors and (2) configure notification routing for Collector down alerts.

Adding the Collector Host into Monitoring

If it isn’t already part of your monitoring operations, add the device on which the Collector is installed into monitoring. This will allow you to keep tabs on CPU utilization, disk space and other metrics important to smooth Collector operation. For more information on adding devices into monitoring, see Adding Devices.

Enabling Collector DataSources on the Host

LogicMonitor provides a series of built-in Collector DataSources that provide insight into a Collector’s operations, performance, and workload. In most cases, these Collector DataSources will be automatically applied to the Collector device when you add it into monitoring. You can verify this is the case by expanding the device in the Resources tree and looking for the “Collector” DataSource group.

Verify Collector DataSources have been applied to the Collector device by expanding the device in the Resources tree and looking for the "Collector" DataSource group

If the Collector DataSources were not automatically applied to the device, you can do so manually by adding the value of “collector” to the device’s system.categories property. For more information on setting properties, see Resource and Instance Properties.

LogicMonitor will now index this device as the host of a Collector, and automatically apply the Collector DataSources to it. Once Collector DataSources are in place, you can configure alerts to warn you when Collector performance is deficient.

Note: Collector DataSources only monitor the device’s preferred Collector (as established in the device’s configurations). The preferred Collector should be the Collector that is installed on that device. Otherwise, the Collector’s metrics will display on the wrong host. For example, if you attempt to monitor Collector A using Collector B (installed on a separate host), then Collector B’s metrics will display in lieu of Collector A’s on Collector A’s host.

Collector DataSources

Migration from Legacy DataSources

In March of 2019, LogicMonitor released a new set of Collector DataSources. If you are currently monitoring Collector hosts using the legacy DataSources, you will not experience any data loss upon importing the newer DataSources in this package. This is because DataSource names have been changed to eliminate module overwriting.

However, you will collect duplicate data and receive duplicate alerts for as long as both sets of DataSources are active. For this reason, we recommend that you disable the legacy Collector DataSources. The legacy DataSources are any Collector DataSources whose names are NOT prefixed with “LogicMonitor_Collector”. If prefixed with “LogicMonitor_Collector”, it is a current Collector DataSource.

When a DataSource is disabled, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSources altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSources, see Disabling Monitoring for a DataSource or Instance.

DataSource Example Highlight: Collector Data Collecting Tasks

One of the Collector DataSources applied is the “Collector Data Collecting Tasks” DataSource. It monitors statistics for collection times, execution time, success/fail rates, and number of active collection tasks. One of the overview graphs available for this DataSource features the top 10 tasks contributing to your Collector’s load, which is extremely useful for identifying the source of CPU or memory usage.

The Top 10 Collection Tasks overview graph is extremely useful for identifying the source of CPU or memory usage

Routing Collector Down Alerts

A Collector is declared down when LogicMonitor’s servers have not heard from it for three minutes. Even though you will likely have a backup Collector in place for when a Collector goes down, it’s never an ideal situation for a Collector to be unexpectedly offline. To minimize downtime and mitigate the risk of interrupted monitoring, ensure that “Collector down” alerts will actively be delivered (as email, text, and so on) to the appropriate individuals in your organization. (These alerts will also be displayed in the LogicMonitor interface. )

Important: When a Collector is declared down, alerts that were triggered by the devices monitored by that Collector before the Collector went down will remain active but new alerts will not be generated while the Collector is down. However, devices that do not fail over to another Collector will ignore the alert generation suppression and may generate Host Status alerts while the Collector status is down.

To route Collector down alerts, open the Collector’s configurations (Settings | Collector | Manage) and specify the following:

Collector Down Escalation Chain. As discussed in Escalation Chains, an escalation chain specifies what people, or groups of people, should be notified of the alert, how they should be notified, and in what order.
Resend interval. From the Send Collector Down Notifications field, set the resend interval for Collector down notifications. You can indicate no resend (i.e. notification is only sent once) or you can indicate the amount of time that should pass before the Collector down alert notifications are escalated to the next stage in the escalation chain. If the alert has reached the final stage or there is only one stage specified in the escalation chain, then this interval, when set, determines how often the alert notification will be resent until it is acknowledged or cleared.

Note: By default, an “Alert clear” notification is automatically delivered to all escalation chain recipients when a downed Collector comes back online. You can override this default by expanding the Collector details and unchecking the Alert on Clear option, shown next. However, if the Collector’s designated escalation chain routes alert notifications to an LM Integration, we recommend that you do not disable this option. For more information, see Alert Rules and Escalation Chains.

Platform

Infrastructure

AIOps & Edwin AI

Cloud & Multi-Cloud

Digital Experience

Logs

Solutions

Business Outcome

Role

Industry

Resources

By Resources

By Topic

Learn the Platform

Company

About Us

Adding an SDT for one Collector

Adding an SDT for multiple Collectors

Restart from LogicMonitor

Restart from Collector Host

Overview

Designating a Failover Collector

Collector Failover

Collector Failback

Automatic Failback to Original Collector

Manual Failback to Original Collector

Overview

Accessing the Collector Debug Facility

Debug Command Syntax

Debug Example: Troubleshooting Data Collection

Adjusting log levels

Changing log file retention

Sending logs to LogicMonitor

Collector Release Tracks

Release Version Conventions

Collector Releases

Active Collector Releases

Archived Collector Releases

Overview

Removing the Collector from Your Account

Manually Removing the Collector from a host Resource

Windows

Linux

Overview

Adding the Collector Host into Monitoring

Enabling Collector DataSources on the Host

Collector DataSources

Migration from Legacy DataSources

DataSource Example Highlight: Collector Data Collecting Tasks

Routing Collector Down Alerts