Snaplex Logs

Overview

You can use Snaplex logs for both troubleshooting and auditory purposes. The properties in the log tab control how the nodes write log messages to the files in the /opt/Snaplogic/run/log directory. These log files provide the backing for the Pipeline logs viewable through the SnapLogic Dashboard.

Logging updates happen with the next heartbeat check. No restart is required.

You can modify the following settings for Snaplex logs in the Create Snaplex and Update Snaplex dialogs:

  • Log Level

  • Log file sizes

  • Backup counts for various logs

Types of Logs

SnapLogic logs are written to the /opt/snaplogic/run/log directory. Two types of processes write events and errors to the logs – JCC and Monitor. The JCC process tracks events, while the Monitor process monitors the health of the JCC. FeedMaster logs are also included.

Log entries

Description

Log entries

Description

jcc.json

The Main log for tracking SnapLogic application events and error messages. 

jcc_error.json

As errors are encountered, verbose error messages are written to this log.

jcc_output.log

As the JCC is booting up, any informational, debugging, and error messages are written to this log.

jcc_access.log

All requests to the node are written to this log. 

jcc.status.log

JCC status is periodically written to this log.

jcc_state_logs.json

The status of the node, connectivity status to the Control Plane, and connectivity between the neighboring nodes of the Snaplex are written to this log.

runtime-log.json

All the executed pipelines on the node are written to this log.

metrics_logs.json

If enabled, this field contains the metrics of the node in JSON format.

monitor.log

As the status of the monitor process initializes, events and errors are written to this log during boot up.

monitor.json

The main log for tracking the monitoring application.

monitor_error.json

Verbose error messages are written to this log, such as the stack traces.

feed_master.json

FeedMaster events and error messages are tracked and written in this log.

feed_master_error.json

As errors are encountered, verbose error messages are written to this log.

feed_master_access.log

All requests to the node are written to this log.

threadDump.dmp

All details of the threads running in the application

The logs are rotated based on file size into the  /opt/snaplogic/run/log/backup directory.

All logs rotate after they become 50MB in size. The logs are compressed and written to the backup directory. Ten of the latest backup files are maintained, while the older files are automatically deleted.

 

You can configure logging for a Snaplex as an Org admin or creator of the Snaplex. Learn more about:

Â