refactor(live-status-gw): reassign log levels #1140
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About the Contributor
This PR is being opened on behalf of TV 2 Norge.
Type of Contribution
This is a:
Code improvement / Log level improvement
Current Behavior
The Live Status Gateway outputs lots of excessive
info
level logs. When in use, it can output hundreds of thousands log entries a day. Some of them inform about individual document updates, heartbeat (sent out every 2 seconds), information about collection handlers and topics receiving or sending updates, etc.New Behavior
info
level is now mostly used for lifecycle events (initialization, connecting/disconnecting, subscribing/unsubscribing). Less relevant messages are demoted todebug
or in few cases tosilly
.Testing Instructions
Other Information
It's a draft, awaiting merge of #1131 after which I'll rebase this to release51Status