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

[Feature request] Add logfile in influxdb.conf to specify log file location #7678

Closed
wei-hai opened this issue Dec 1, 2016 · 3 comments
Closed

Comments

@wei-hai
Copy link

wei-hai commented Dec 1, 2016

Proposal:
Add logfile in influxdb.conf to specify log file location like that in telegraf
Current behavior:
The latest version writes log via systemd journal
Desired behavior:
Provide an option to use the old way for logging
Use case:
We use Telegraf's plugin tail and logparser to find error message from influxdb's log file and they cannot work with journalctl, so it would be flexible to provide an option to explicitly specify where the log file is.

@jsternberg
Copy link
Contributor

jsternberg commented Dec 1, 2016

It might be most appropriate to do this as part of the change to structured logging that's being done in #7036.

The initial PR for that won't do what this issue is requesting, but it's a very small step to add that functionality afterward.

@e-dard
Copy link
Contributor

e-dard commented Dec 2, 2016

I'm 👎 on adding functionality to log to files. I don't think the database should be concerning itself with that. If it's necessary to redirect database logs to file(s) then using shell redirection and/or tools like tee seems like the best way to do this.

@pauldix
Copy link
Member

pauldix commented Jan 25, 2017

Does the information on this page give a good answer for how to work with the InfluxDB output in log files? https://docs.influxdata.com/influxdb/v1.2/administration/logs/

@wei-hai wei-hai closed this as completed Jun 10, 2017
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

4 participants