Managing Collector Logs

You can control how much information is logged by your Collector and how long the log files are retained.

Collector Log Upload Behavior

Collector log files are uploaded and stored under the company-level upload directory. The files are stored using the following naming pattern:

stamp_<lastModifiedTime>.<collectorId>.<filename>

For example, for Collector ID 48721, a log file might be named:

stamp_1783411000000.48721.wrapper.1.log.zip

When a new log file is uploaded, the existing replacement logic checks for previously uploaded files with the same filename and replaces only the first matching file, regardless of the Collector it originated from. As a result, if multiple Collectors under the same company upload logs with the same filename, such as wrapper.log.zip, the recently uploaded file replaces a previously uploaded file from another Collector. The replacement logic deletes only the first matching file and not all matching files.

Additionally, a single uploaded filename cannot match multiple Collector log files. For rotated logs, LogicMonitor appends a sequence number, making each filename unique. For example, wrapper.1.log.zip and wrapper.2.log.zip. Therefore, wrapper.log.zip can only match wrapper.log.zip and not wrapper.1.log.zip or wrapper.2.log.zip. 

Collector Log Upload and Replacement Logic Scenario

Assumptions

Collector ID 48721 uploads the following log files:

stamp_1783411000000.48721.wrapper.1.log.zip
stamp_1783411100000.48721.wrapper.2.log.zip
stamp_1783411200000.48721.wrapper.log.zip
stamp_1783411300000.48721.watchdog.log.zip
stamp_1783411400000.48721.upgrade.log.zip

Later, Collector ID 48722 uploads the following log files:

stamp_1783412000000.48722.wrapper.log.zip
stamp_1783412100000.48722.watchdog.log.zip

Replacement Logic

Before saving each new file, LogicMonitor checks for an existing file whose filename matches the newly uploaded filename. The files are checked based only on the filename field.

• When Collector ID 48722 uploads wrapper.log.zip, the replacement logic finds a matching filename, wrapper.log.zip, uploaded by Collector ID 48721 and deletes it.
  stamp_1783411200000.48721.wrapper.log.zip
• Similarly, when Collector ID 48722 uploads watchdog.log.zip, the replacement logic finds a matching filename, watchdog.log.zip, uploaded by Collector ID 48721 and deletes it.
  stamp_1783411300000.48721.watchdog.log.zip

Result

The following log files are available in the company upload directory:

stamp_1783411000000.48721.wrapper.1.log.zip
stamp_1783411100000.48721.wrapper.2.log.zip
stamp_1783411400000.48721.upgrade.log.zip
stamp_1783412000000.48722.wrapper.log.zip
stamp_1783412100000.48722.watchdog.log.zip

Collector Log File Matching and Replacement Logic Scenario

Assumptions

The following log files from Collector IDs 48721 and 48723 are already uploaded to the company upload directory:

stamp_1783411300000.48721.watchdog.log.zip
stamp_1783411310000.48721.wrapper.log.zip
stamp_1783411320000.48723.watchdog.log.zip

Later, Collector ID 48722 uploads the following log files:

stamp_1783414000000.48722.upgrade.log.zip
stamp_1783414100000.48722.watchdog.log.zip

Replacement Logic

When matching files, the system returns a list of files with the same target filename and selects the first result from the list for replacement.

The system usually finds only a single matching file based on the unique suffix added to the filenames, and the replacement logic replaces the matching file.

When Collector ID 48722 looks for watchdog.log.zip to determine the file to replace, it selects the first entry from the following matching results:

stamp_1783411300000.48721.watchdog.log.zip
stamp_1783411320000.48723.watchdog.log.zip
stamp_1783414100000.48722.watchdog.log.zip

The first log file from the matching results, stamp_1783411300000.48721.watchdog.log.zip, is replaced.

Result

The following log files are available in the company upload directory:

stamp_1783411310000.48721.wrapper.log.zip
stamp_1783411320000.48723.watchdog.log.zip
stamp_1783414000000.48722.upgrade.log.zip
stamp_1783414100000.48722.watchdog.log.zip

Adjusting Log Level

You can 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. 

1. In LogicMonitor, navigate to Settings > Collectors.
2. Under the Collectors tab, select the Collector whose log level you want to adjust.  
3. Select the Logs tab and then select Manage Collector Logs.
   
   The log levels on a per component basis for that Collector display.
   

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 logs 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 resources, and as such is typically only recommended for debugging purposes.
• Debug—Logs detailed information about Collector tasks (not as much information as trace log level). The debug log level can make it easier to identify an issue and track the root cause.
• Info—It is the default log level. It logs basic information about Collector tasks.
• Warn—Information is only logged when something is not right, but it may not be causing an issue yet.
• Error—Information is only logged when something is wrong.
• Disable—No information is logged.

For example, you might write a script datasource and your Collector is getting no data, but you do not know the issue. You can 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.

Modifying Log File Retention Property

Collector log files are rotated based on size, and not date. By default, there are three log files of 64M each. If needed, you can change these numbers 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.

1. In LogicMonitor, navigate to Settings > Collectors.
2. Under the Collectors tab, select the Collector whose log file retention property you want to modify.
3. Select  More and then select Collector Configuration.
4. Select the Wrapper Config tab and locate the Wrapper logging properties and
5. Modify the values in the wrapper.logfile.maxsize and wrapper.logfile.maxfiles properties.
   
6. Select Save and Restart to apply the changes.

Sending Logs to LogicMonitor

You can send logs to LogicMonitor support. You can collaborate with the support team and enable them to look through the Collector log files.

1. In LogicMonitor, navigate to Settings > Collectors.
2. Under the Collectors tab, select the Collector whose logs you want to send.  
3. Select  More and then select Send Logs to LogicMonitor.
   
   Logs that are sent to LogicMonitor support display under the Logs section for that Collector. You can filter them based on the time range to limit the result.