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

Reduce Log Output? #2989

Closed
mrjgreen opened this issue Jun 15, 2015 · 4 comments
Closed

Reduce Log Output? #2989

mrjgreen opened this issue Jun 15, 2015 · 4 comments

Comments

@mrjgreen
Copy link

I was wondering if there is an option to limit the amount of logging output from the server, especially when using the UDP collection handler.

I'm getting thousands of rows of output that look like this:

[udp] 2015/06/15 16:07:28 Wrote a batch of 10 points to test
[udp] 2015/06/15 16:07:28 Wrote a batch of 10 points to test
[udp] 2015/06/15 16:07:28 Wrote a batch of 10 points to test
[udp] 2015/06/15 16:07:28 Wrote a batch of 10 points to test

I tried adding a log-enabled = false directive to the [udp] section but this didn't work either. This seems odd, I would have expected some consistency between the different handlers.

I notice in earlier versions there were options in the config file for setting the log level. These no longer seem to have any effect... The ability to log only messages above a configured level seems like it would be useful? Has there been a conscious decision to remove this in v0.9 or has it just not yet been implemented?

[logging]
# logging level can be one of "debug", "info", "warn" or "error"
level  = "info"
file   = "influxdb.log"         # stdout to log to standard out

Sorry if I'm asking questions that have already been answered elsewhere... I had a look through the closed issues but couldn't find anything.

If there is a requirement here for a new feature I'd be happy to try and work towards a PR

Cheers

@mrjgreen mrjgreen changed the title Reduce Log Level? Reduce Log Output? Jun 15, 2015
@otoolep
Copy link
Contributor

otoolep commented Jun 15, 2015

Thanks @mrjgreen -- this is excessive we should not be logging each batch.

otoolep added a commit that referenced this issue Jun 15, 2015
@otoolep
Copy link
Contributor

otoolep commented Jun 15, 2015

Fixed by #2993

@otoolep
Copy link
Contributor

otoolep commented Jun 15, 2015

All fixed.

@otoolep otoolep closed this as completed Jun 15, 2015
@mrjgreen
Copy link
Author

Thats great! And thanks for such quick resolution!

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

No branches or pull requests

2 participants