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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parser friendly, more complete logs #97

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

BuonOmo
Copy link
Member

@BuonOmo BuonOmo commented Jun 17, 2021

Reaper status logs are printed even if we are killing a worker, and they
show information for each worker. Information is presented in a key=value
fashion which is way easier to parse, and correctly handled by most log
analysis tools.

Since this is breaking former log parsing, I've taken the liberty to
also clarify logs, showing that master is included in the total.


NOTES:

  • I've seen in the mean time that this last part is already in Refine worker termination and rolling restart log messages聽#96,
    I'd be glad to leave rebase on top of if, leaving the credit to the
    original author,
  • Seeing there was no test for set_workers, I did not add any. Yet
    I could add some for set_master_memory if it feels right.
  • I may make this an option if you are too worried about breaking actual
    parsing. Yet I don't think it is necessary!

Thank you for that very useful gem 馃檪 (and all of your work!)

Ulysse

Reaper status logs are printed even if we are killing a worker, and they
show information for each worker. Information is presented in a key=value
fashion which is way easier to parse, and correctly handled by most log
analysis tools.

Since this is breaking former log parsing, I've taken the liberty to
also clarify logs, showing that master is included in the total.

Signed-off-by: Ulysse Buonomo <buonomo.ulysse@gmail.com>
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.

None yet

1 participant