# Log settings

By default, &repmgr; and &repmgrd; write log output to `STDERR`. An alternative log destination can be specified (either a file or `syslog`).

The &repmgr; application itself will continue to write log output to `STDERR` even if another log destination is configured, as otherwise any output resulting from a command line operation will "disappear" into the log.

This behaviour can be overriden with the command line option `--log-to-file`, which will redirect all logging output to the configured log destination. This is recommended when &repmgr; is executed by another application, particularly &repmgrd;, to enable log output generated by the &repmgr; application to be stored for later reference.

`log_level` (`string`)

- One of `DEBUG`, `INFO`, `NOTICE`, `WARNING`, `ERROR`, `ALERT`, `CRIT` or `EMERG`.

  Default is `INFO`.

  Note that `DEBUG` will produce a substantial amount of log output and should not be enabled in normal use.

`log_facility` (`string`)

- Logging facility: possible values are `STDERR` (default), or for syslog integration, one of `LOCAL0`, `LOCAL1`, `...`, `LOCAL7`, `USER`.

`log_file` (`string`)

- If repmgr-conf-log-facility is set to `STDERR`, log output can be redirected to the specified file.

  See repmgrd-log-rotation for information on configuring log rotation.

`log_status_interval` (`integer`)

- This setting causes &repmgrd; to emit a status log line at the specified interval (in seconds, default `300`) describing &repmgrd;'s current state, e.g.:

            [2018-07-12 00:47:32] [INFO] monitoring connection to upstream node "node1" (ID: 1)