...
Log entries | Description |
---|---|
| The Main log for tracking SnapLogic application events and error messages. |
| As errors are encountered, verbose error messages are written to this log. |
| As the JCC service is booting up, any informational, debugging, and error messages are written to this log. |
| All requests to the node are written to this log. |
| The JCC service status is periodically written to this log. |
| The status of the node, connectivity status to the Control Planecontrol plane, and connectivity between the neighboring nodes of the Snaplex are written to this log. |
| The status of the logging service when the JCC service is booted. When the node is started, the logging service is also started. |
| All the executed pipelines on the node are written to this log. |
| If enabled, this field contains the metrics of the node in JSON format. |
| As the status of the monitor process initializes, events and errors are written to this log during boot up. |
| The main log for tracking the monitoring application. |
| Verbose error messages are written to this log, such as the stack traces. |
| This contains the unique node ID (ccid) and label (ccLabel) of the Node. |
| FeedMaster events and error messages are tracked and written in this log. |
| As errors are encountered, verbose error messages are written to this log. |
| All requests to the node are written to this log. |
| This is the FeedMaster counterpart to the |
| This is the FeedMaster counterpart to the |
| This log collects the status of Scheduled Tasks running on the node. |
| This log collects the status of Ultra Tasks running on the node. |
| 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.
...