45/// `default` logger is the one used for `LOG_*`.
46///
47/// ### Logs output
48/// You can specify where logs are written in the `file_path` option:
49/// - Use <tt>file_path: '\@stdout'</tt> to write your logs to standard output stream;
50/// - Use <tt>file_path: '\@stderr'</tt> to write your logs to standard error stream;
51/// - Use <tt>file_path: '\@null'</tt> to suppress sending of logs;
52/// - Use <tt>file_path: /absolute/path/to/log/file.log</tt> to write your logs to file. Use USR1 signal or @ref server::handlers::OnLogRotate to reopen files after log rotation;
53/// - Use <tt>file_path: 'unix:/absolute/path/to/logs.sock'</tt> to write your logs to unix socket. Socket must be created before the service starts and closed by listener after service is shut down.
54///
55/// For sending logs directly to an otlp (opentelemetry) sink, see @ref opentelemetry.
56///
57/// Customization of log sinks beyond the ones listed above is not supported at the moment.
58///
59/// ### Logs format
60/// You can specify in what format logs are written in the `format` option:
61/// - Use `format: tskv` for traditional optimized userver-flavoured TSKV representation. See @ref utils::encoding::TskvParser for the exact format specification;
62/// - Use `format: ltsv` for the same format, with `:` instead of `=` for key-value separator;
63/// - Use `format: raw` for TSKV logs with timestamp and other default tags stripped, useful for @ref custom_loggers "custom loggers";
64/// - Use `format: json` for JSON logs. @ref logging::JsonString can be used with this format for rich hierarchical log tags;
65/// - Use `format: json_yadeploy` for JSON logs with a slightly different structure.
66///
67/// When sending logs using @ref opentelemetry, logs are written to otlp protobuf messages.
68///
69/// Customization of log formats beyond the ones listed above is not supported at the moment.