-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Use rfc3339 timestamps w/ timezone in log output #1564
Comments
If you're using an OS which uses systemd, personally I'd recommend editing the systemd service file and remove the redirection to the log files and let it instead go to journald. This offers a lot more flexibility in what you can do with the logs, and will also solve the timestamp issue. The benefit of both these solutions is that they're standard practices. There's a good chance you're already consuming journald/syslog data, and so you don't need any telegraf specific configuration for logstash to read the logs. |
There are timestamps?:
|
Gah sorry, I meant timezones not timestamps. |
OK |
closes #1564 also add unit and benchmark tests
closes #1564 also add unit and benchmark tests
closes #1564 also add unit and benchmark tests
closes #1564 also add unit and benchmark tests
closes #1564 also add unit and benchmark tests
Currently Telegraf logs (written to
/var/log/telegraf/telegraf.log
at least for us) do not contain the timestamp. This makes it difficult to accurately ingest the logs into a logging pipeline such as Logstash.The text was updated successfully, but these errors were encountered: