From 91d9621761d422e8be8303184d8246bc4dc94ab1 Mon Sep 17 00:00:00 2001 From: pama-ibm Date: Wed, 6 Jan 2021 13:33:30 -0500 Subject: [PATCH] Add more details to logging specification examples Signed-off-by: pama-ibm (cherry picked from commit eec934181ace1b929af7a194ff8b45bfd275e1da) --- docs/source/logging-control.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/source/logging-control.rst b/docs/source/logging-control.rst index 7c3f8e30d4d..03af6f4c587 100644 --- a/docs/source/logging-control.rst +++ b/docs/source/logging-control.rst @@ -74,6 +74,12 @@ syntax. Examples of specifications: warning:msp,gossip=warning:chaincode=info - Default WARNING; Override for msp, gossip, and chaincode chaincode=info:msp,gossip=warning:warning - Same as above +.. note:: Logging specification terms are separated by a colon. If a term does not include a specific logger, for example `info:` then it is applied as the default log level + across all loggers on the component. The string `info:dockercontroller,endorser,chaincode,chaincode.platform=debug` sets + the default log level to `INFO` for all loggers and then the `dockercontroller`, `endorser`, `chaincode`, and + `chaincode.platform` loggers are set to `DEBUG`. The order of the terms does not matter. In the examples above, + the second and third options produce the same result although the order of the terms is reversed. + Logging format -------------- @@ -119,4 +125,3 @@ chaincode container using standard commands for your container platform. .. Licensed under Creative Commons Attribution 4.0 International License https://creativecommons.org/licenses/by/4.0/ -