Skip to content

Accessing the Log Files of the sedex Client via Container Logs

The logs of the sedex Client can be retrieved using the standard container logs mechanism.

The log files should be monitored and analyzed

The logs of the sedex Client provide detailed information about running processes and important events. The log files should be monitored and analyzed - especially in case of errors.

The combined sedex Client logs are written to the standard output stdout and thus can be accessed using the the standard container mechanisms for logs.

The following example shows how to continuously display the logs using docker logs command:

$ docker logs sedex-client --follow
14:21:27 INFO Adapterlog - 14:21:27 DEBUG ThrottlingPriorityMessageScheduler - No new messages in outbox. Skipping scheduling of messages to be sent.
14:21:57 INFO Adapterlog - 14:21:57 DEBUG ThrottlingPriorityMessageScheduler - Begin scheduling of messages
14:21:57 INFO Adapterlog - 14:21:57 DEBUG ThrottlingPriorityMessageScheduler - No new messages in outbox. Skipping scheduling of messages to be sent.
14:22:27 INFO Adapterlog - 14:22:27 DEBUG ThrottlingPriorityMessageScheduler - Begin scheduling of messages
14:22:27 INFO Adapterlog - 14:22:27 DEBUG ThrottlingPriorityMessageScheduler - No new messages in outbox. Skipping scheduling of messages to be sent.
14:22:57 INFO Adapterlog - 14:22:57 DEBUG ThrottlingPriorityMessageScheduler - Begin scheduling of messages
14:22:57 INFO Adapterlog - 14:22:57 DEBUG ThrottlingPriorityMessageScheduler - No new messages in outbox. Skipping scheduling of messages to be sent.
[...]