You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Integrate the flogging package with gossip logging, making the gossip
logging control consistent with the logging control methods of the core
fabric modules.
- Support all the control methods described in the logging control
document when gossip is in a peer process, see:
https://hyperledger-fabric.readthedocs.io/en/latest/Setup/logging-control/
For example, if the gossip modules is called by `peer node start`,
the gossip logging level can be overridden in these ways listed
below, from strongest to weakest:
1. The --logging-level=<level> command line option.
2. The CORE_LOGGING_LEVEL env variable.
3. The CORE_LOGGING_NODE env variable.
4. The "logging.node" spec defined in the peer/core.yaml file.
And a command like:
peer logging setlevel <module> <log level> [flags]
can set logging level for a specified module on the fly.
- Fallback to gossip's default logging level and format when gossip is
not in a peer process. The current default logging level is set to
"WARNING", and the default logging format is taken from the flogging
package.
Resolves FAB-1217.
Change-Id: I57e0d5ca4dc10a4774e3ac20e2e71e6ff85e18b8
Signed-off-by: Xiaoyi Wang <[email protected]>
Signed-off-by: Ray Chen <[email protected]>
s.logger.Infof("Updating node metadata information, current ledger sequence is at = %d, next expected block is = %d", state.LedgerHeight, s.payloads.Next())
0 commit comments