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

Auto detect of logging already initialised #746

Closed
ruflin opened this issue Jan 18, 2016 · 1 comment
Closed

Auto detect of logging already initialised #746

ruflin opened this issue Jan 18, 2016 · 1 comment

Comments

@ruflin
Copy link
Member

ruflin commented Jan 18, 2016

When starting up a beat, it can happen that logp is not configured / initialised yet. In case logp is not configured it should write to the standard output by default using fmt.Errorf. This makes it possible to always use logp also on start instead of switching to fmt.Printf in some cases.

All usage of fmt.* should be removed for cleanup

@ruflin
Copy link
Member Author

ruflin commented Feb 26, 2018

This has been fixed since then.

@ruflin ruflin closed this as completed Feb 26, 2018
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