Skip to content

Commit 01aa829

Browse files
committed
[FAB-3145] Override log level for ledger at peer start
This CR overrides the log level for all modules with ledger in their module name during peer start. The value can be set in core.yaml using `logging.ledger` or by using the CORE_LOGGING_LEDGER environment variable. Change-Id: Ia869573d7bb13a93468b70e5480e996b351775cb Signed-off-by: Will Lahti <[email protected]>
1 parent 5f91834 commit 01aa829

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

peer/node/start.go

+3-3
Original file line numberDiff line numberDiff line change
@@ -264,9 +264,9 @@ func serve(args []string) error {
264264
logger.Infof("Started peer with ID=[%s], network ID=[%s], address=[%s]",
265265
peerEndpoint.Id, viper.GetString("peer.networkId"), peerEndpoint.Address)
266266

267-
// set the logging level for specific modules defined in core.yaml.
268-
// TODO Add calls to set 'ledger' module loggers
269-
overrideLogModules := []string{"msp", "gossip"}
267+
// set the logging level for specific modules defined via environment
268+
// variables or core.yaml
269+
overrideLogModules := []string{"msp", "gossip", "ledger"}
270270
for _, module := range overrideLogModules {
271271
err = common.SetLogLevelFromViper(module)
272272
if err != nil {

0 commit comments

Comments
 (0)