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

Cleanup: moves most console log statements into Observability classes #152

Merged
merged 5 commits into from
Nov 2, 2024

Conversation

robacarp
Copy link
Collaborator

@robacarp robacarp commented Nov 2, 2024

I spent some time cleaning up the Log output, specifically reducing redundant labeling. On the way it became clear that the real place for most of these logs is in the Observability modules, not on the runner itself. This has proven to be a nice refactor, clarifying the purpose of the Observability mobule and distilling the runner logic by removing the fluff required to inform users of the state.

This changes the log output:

The overseer boot message used to be:
INFO - mosquito.runners.overseer.4315742080: Overseer<4315742080> is starting
Now the message is simply:
INFO - mosquito.overseer: starting

Similarly, messages from QueueList, Executor, Coordinator, now lack the .runners. segment of the tag. Where a runner is likely to be the only instance of that runner within a mosquito process (as with overseer exemplified above) the object id is no longer part of the tag either.

@robacarp robacarp merged commit e20a4b9 into master Nov 2, 2024
3 checks passed
@robacarp robacarp deleted the adds_mosquito_api branch November 2, 2024 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant