fabric-docs-i18n icon indicating copy to clipboard operation
fabric-docs-i18n copied to clipboard

[ja_JP] Operations Guides / Logging Control

Open shimos opened this issue 2 years ago • 0 comments

Original HTML: https://hyperledger-fabric.readthedocs.io/en/release-2.5/logging-control.html Original Source: https://github.com/hyperledger/fabric/blob/e1e8e2e52aa4fc543360d245fe6554a0eaf81183/docs/source/logging-control.rst

diff --git a/docs/source/logging-control.rst b/docs/source/logging-control.rst
index 03af6f4c5..b1e6fdc1b 100644
--- a/docs/source/logging-control.rst
+++ b/docs/source/logging-control.rst
@@ -35,7 +35,7 @@ generating logs.
    2018-11-01 15:32:38.357 UTC [peer] func1 -> INFO 007 Returning peer0.org1.example.com:7051
 
 An arbitrary number of loggers can be created at runtime, therefore there is
-no "master list" of loggers, and logging control constructs can not check
+no "global list" of loggers, and logging control constructs can not check
 whether logging loggers actually do or will exist.
 
 Logging specification
@@ -94,6 +94,41 @@ a format string, such as the default
 to print the logs in a human-readable console format. It can be also set to
 ``json`` to output logs in JSON format.
 
+Typical debug levels
+--------------------
+
+This section provides some typical log levels to debug various areas of a peer node or ordering service node by setting the ``FABRIC_LOGGING_SPEC`` environment variable.
+
+Peer smart contract debug:
+
+::
+
+    FABRIC_LOGGING_SPEC=info:dockercontroller,endorser,chaincode,chaincode.platform=debug
+
+Peer private data debug:
+
+::
+
+    FABRIC_LOGGING_SPEC=info:kvledger,ledgerstorage,transientstore,pvtdatastorage,gossip.privdata=debug
+
+Peer ledger and state database debug:
+
+::
+
+    FABRIC_LOGGING_SPEC=info:kvledger,lockbasedtxmgr,ledgerstorage,stateleveldb,statecouchdb,couchdb=debug
+
+Peer full debug, with the noisy components set to info:
+
+::
+
+    FABRIC_LOGGING_SPEC=debug:cauthdsl,policies,msp,grpc,peer.gossip.mcs,gossip,leveldbhelper=info
+
+Ordering node full debug, with the noisy components set to info:
+
+::
+
+    FABRIC_LOGGING_SPEC=debug:cauthdsl,policies,msp,grpc,orderer.consensus.etcdraft,orderer.common.cluster,orderer.common.cluster.step,common.configtx,blkstorage=info
+
 
 Chaincode
 ---------

shimos avatar Sep 28 '23 01:09 shimos