Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change verbosity of state machine logs to trace #1597

Merged
merged 4 commits into from
Aug 26, 2022

Conversation

abernix
Copy link
Member

@abernix abernix commented Aug 24, 2022

This changes the verbosity of messages like transitioned to starting from
the info level to the trace level since messages about the state machine
aren't necessary user-facing information during normal operation.

I waffled a bit on whether this should be trace or debug. To some degree this seems like deeper inards of the Router than most people should ever need to encounter. Since I think debugging the state machine might be a a particularly detailed operation in the general sense, I chose to use trace since it's my undersatnding the user can still use other log/env filters to tune the scope of what they're receiving log messages for, even at the trace level.

Anyway, I'm happy to change it to debug — just say the word.

Closes #1578

This changes the verbosity of messages like `transitioned to starting` from
the `info` level to the `trace` level since messages about the state machine
aren't necessary user-facing information during normal operation.

Closes #1578
@github-actions

This comment has been minimized.

tracing::info!("transitioned to {}", &new_state);
tracing::trace!("transitioned to {}", &new_state);
Copy link
Member Author

Choose a reason for hiding this comment

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

@o0Ignition0o seemed okay with debug in his comment on the original issue. I considered it.

My claim would be that it's better to make things more verbose if necessary and bury as much extra distraction as we can unless it's proven consistently necessary to make it louder at less-noisy levels.

@abernix abernix requested review from garypen, o0Ignition0o and bnjjj and removed request for garypen August 24, 2022 09:18
@o0Ignition0o
Copy link
Contributor

I think we can merge this once the NEXT_CHANGELOG conflict is dealt with

@Geal Geal enabled auto-merge (squash) August 26, 2022 12:50
@Geal Geal merged commit 554b033 into main Aug 26, 2022
@Geal Geal deleted the abernix/change-state-machine-loglevel branch August 26, 2022 19:09
@abernix abernix mentioned this pull request Aug 29, 2022
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.

change the state machine log verbosity level to be trace
5 participants