Skip to content

Conversation

@mkysel
Copy link
Collaborator

@mkysel mkysel commented Jan 9, 2026

Adjust logging levels in contracts.GroupMessageStorer.StoreLog, contracts.IdentityUpdateStorer.StoreLog, common.IndexLogs, and rpc_streamer.RPCLogStreamer.watchContract, adding 5-minute Info progress logs and moving termination logs to Info

Raises operational log levels to Info/Warn, adds periodic 5-minute Info progress logs for the latest block, and guards Debug logs behind a zap.DebugLevel check.

📍Where to Start

Start with common.IndexLogs in log_handler.go.


Macroscope summarized 5402e97.

@mkysel mkysel requested a review from a team as a code owner January 9, 2026 17:45
"inserting message from contract",
utils.TopicField(topicStruct.String()),
)
if s.logger.Core().Enabled(zap.DebugLevel) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this functionally do anything, other than save a tiny bit of execution on generating the topicField?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nope. just a tiny optimization. Might be a good pattern to get in the habit of using.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specially useful when using zap.Any(), because avoids using reflection outside Debug loglevel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants