8000 logs: adopt the `Warn` level when best suited · Issue #4453 · cometbft/cometbft · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
logs: adopt the Warn level when best suited #4453
Open
@cason

Description

@cason

With the introduction of slog (#4374), we have an additional Warn log level available for all CometBFT components.

We have in the code base several situations where this new level would be best suited, for instance:

./config/config.go: // CheckDeprecated returns any deprecation warnings. These are printed to the operator on startup.
./node/node.go:		logger.Info("warning: cannot verify appHash. Verification will happen when node boots up!")
./p2p/pex/known_address.go:			// log.Warn(Fmt("Bucket already exists in ka.Buckets: %v", ka))
./internal/consensus/wal.go:		wal.Logger.Error("Error writing msg to consensus wal. WARNING: recover may not be possible for the current height",

We should adapt the logging level in order to render some messages more visible, with the introduction of this new log level.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P:operator-experiencePriority: Improve experience for operatorslogsAnything relating to logging

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0