docs: Use "error" to use standard log level value (#13507)

* docs: Use "error" to use standard log level value
This commit is contained in:
David Yu 2022-06-20 16:07:38 -07:00 committed by GitHub
parent 6980975d6f
commit b724f8b3ab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions

View File

@ -32,6 +32,6 @@ Usage: `consul monitor [options]`
- `-log-level` - The log level of the messages to show. By default this
is "info". This log level can be more verbose than what the agent is
configured to run at. Available log levels are "trace", "debug", "info",
"warn", and "err".
"warn", and "error".
- `-log-json` - Toggles whether the messages are streamed in JSON format.
By default this is false.

View File

@ -229,7 +229,7 @@ if desired.
provided, this will be disabled. Defaults to "72h".
- `-log-level` - Controls verbosity of snapshot agent logs. Valid options are
"TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
"trace", "debug", "info", "warn", "error". Defaults to "info".
- `-service` - The service name to used when registering the agent with Consul.
Registering helps monitor running agents and the leader registers an additional

View File

@ -468,7 +468,7 @@ information.
- `-log-level` ((#\_log_level)) - The level of logging to show after the
Consul agent has started. This defaults to "info". The available log levels are
"trace", "debug", "info", "warn", and "err". You can always connect to an agent
"trace", "debug", "info", "warn", and "error". You can always connect to an agent
via [`consul monitor`](/commands/monitor) and use any log level. Also,
the log level can be changed during a config reload.