Logging
Configuration for logging.
By default, logs append to a single file and rollover at the end of each day.
Parameters
The minimum level of log messages to show. If set to Level.OFF, no logs will be shown. See the Level enum for more details. Level.DEBUG is a decent balance of verbosity and usefulness. Level.TRACE is incredibly verbose, and is mostly intended for locally debugging. It probably shouldn't be used in production, but it can be helpful when trying to debug a particularly tricky issue (such as a CORS misconfiguration or a case where the ktor server is sending you back 403s).
If true, logs will be written to stdout/stderr.
If true, logs will be written to a file (in addition to stdout/stderr). If false, logs will only be written to stdout/stderr. If false, the other file-related properties in this class will essentially be ignored.
The root directory where logs will be stored. If you change this to a directory that will contain other files besides just logs, consider setting clearLogsOnStart to false.
If true, all existing files under the log root will be deleted when a server is started in dev mode. Be careful if you changed logRoot to a path with non-log files in it!
The base name of the log file. A log suffix will automatically be added. Later, if the logs roll over, they'll be archived, and the base name will be used again in that context.
The maximum number of log files to keep before old entries get deleted. Pass in null (or 0) to indicate unbounded file count.
The maximum size of all log files before old entries get deleted. Pass in null (or "0b") to indicate unbounded size.
If true, log files will be compressed when they roll over.