Always ignore kombu library "heartbeat_tick" debug log messages #4557
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.
In the past, I opened a change so we ignore kombu
heartbeat_tick
debug log messages which are logged every 2 ms by default when either--debug
service command line flag is used or whensystem.debug
st2.conf config option is set toTrue
.While troubleshooting release workflows on st2cicd server, I found an edge case.
If
DEBUG
log level is set in the service logging config, but--debug flag
/system.debug
config option is not used, those messages won't be ignored.This is not desired, because those messages will pollute the logs and make it very hard to find other actual important DEBUG and non DEBUG log messages.
Here is an example from st2workflowengine.log on st2cicd:
TODO