Logs¶
Reading What's Happening
By default, logs are written to stdout, in text format.
Configuration¶
General¶
Traefik logs concern everything that happens to Traefik itself (startup, configuration, events, shutdown, and so on).
filePath
¶
By default, the logs are written to the standard output.
You can configure a file path instead using the filePath
option.
# Writing Logs to a File
log:
filePath: "/path/to/traefik.log"
# Writing Logs to a File
[log]
filePath = "/path/to/traefik.log"
# Writing Logs to a File
--log.filePath=/path/to/traefik.log
format
¶
By default, the logs use a text format (common
), but you can also ask for the json
format in the format
option.
# Writing Logs to a File, in JSON
log:
filePath: "/path/to/log-file.log"
format: json
# Writing Logs to a File, in JSON
[log]
filePath = "/path/to/log-file.log"
format = "json"
# Writing Logs to a File, in JSON
--log.filePath=/path/to/traefik.log
--log.format=json
level
¶
By default, the level
is set to ERROR
.
Alternative logging levels are DEBUG
, INFO
, WARN
, ERROR
, FATAL
, and PANIC
.
log:
level: DEBUG
[log]
level = "DEBUG"
--log.level=DEBUG
Log Rotation¶
Traefik will close and reopen its log files, assuming they're configured, on receipt of a USR1 signal.
This allows the logs to be rotated and processed by an external program, such as logrotate
.
Warning
This does not work on Windows due to the lack of USR signals.
Using Traefik OSS in Production?
If you are using Traefik at work, consider adding enterprise-grade API gateway capabilities or commercial support for Traefik OSS.
Adding API Gateway capabilities to Traefik OSS is fast and seamless. There's no rip and replace and all configurations remain intact. See it in action via this short video.