Commit 50aec3fc authored by Matthew Sykes's avatar Matthew Sykes
Browse files

[FAB-9131] Update peer logging doc and examples



Change-Id: I1105be1769d60ec274fcbcc5e975acdde0fe20c3
Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
parent 97215fa6
......@@ -54,8 +54,8 @@ The top level `peer` command has the following flags:
This flag sets the logging level for a peer when it is started.
There are six possible values for `<string>` : `debug`, `info`, `notice`,
`warning`, `error`, and `critical`.
There are six possible values for `<string>` : `debug`, `info`, `warning`,
`error`, `panic`, and `fatal`.
If `logging-level` is not explicitly specified, then it is taken from the
`CORE_LOGGING_LEVEL` environment variable if it is set. If
......
......@@ -71,10 +71,10 @@ Flag details
This flag sets the log level for the single peer command it is supplied with.
Once the command has been executed, the log level will not persist. There are
six possible log levels: ``debug``, ``info``, ``notice`, ``warning``, ``error``,
and ``critical``. Note that there is no single logging level for the peer. You
six possible log levels: ``debug``, ``info``, ``warning``, ``error``, ``panic``,
and ``fatal``. Note that there is no single logging level for the peer. You
can find the current logging level for a specific component on the peer by
running ``peer logging getlevel <component-name``. The defaults are defined in
running ``peer logging getlevel <component-name>``. The defaults are defined in
``sampleconfig/core.yaml`` if you'd like to take a look at what logging levels are
set if the system admin doesn't modify anything.
......
......@@ -25,7 +25,7 @@ logging:
# subcommands, the defaults also apply to all subcommands of the command.
# Valid logging levels are case-insensitive strings chosen from
# CRITICAL | ERROR | WARNING | NOTICE | INFO | DEBUG
# FATAL | PANIC | ERROR | WARNING | INFO | DEBUG
# The logging levels specified here can be overridden in various ways,
# listed below from strongest to weakest:
......
......@@ -14,7 +14,7 @@ logging:
# Valid logging levels are case-insensitive strings chosen from
# CRITICAL | ERROR | WARNING | NOTICE | INFO | DEBUG
# FATAL | PANIC | ERROR | WARNING | INFO | DEBUG
# The overall default logging level can be specified in various ways,
# listed below from strongest to weakest:
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment