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

Improve logging coverage and flexibility #30

Closed
tgross opened this issue May 10, 2016 · 1 comment
Closed

Improve logging coverage and flexibility #30

tgross opened this issue May 10, 2016 · 1 comment

Comments

@tgross
Copy link
Contributor

tgross commented May 10, 2016

In #28, debugging the problem could have been improved by having better logging in the preStart handler. Also, in #28 (comment) @tgross wrote:

It looks like there's a couple spots we could hook in more logging too. The balance of debug vs info has been hard to get right; I'm wondering if we should keep the last N messages of a DEBUG level in a ring log with some mechanism to dump them to stdout even if the instances are logging at INFO.

Because we don't have a persistent daemon for the manage.py this might be easier said than done. We could always just have a file that we truncate if it gets above size N. Or perhaps just move all the logging around replication setup to INFO, although I'm not wild about that solution either.

@tgross
Copy link
Contributor Author

tgross commented Aug 29, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant