-
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
Telegraf Syslog plugin. #4335
Comments
@bogski87 thanks for opening this issue. could you add some sample log lines and the relevant syslog (or rsyslog) conf files as well? |
Hi @russorat , sure thing. I don't have anywhere to host the configs so it is a cut and paste job unfortunately. contents of /etc/rsyslog.conf
Contents of /etc/rsyslog.d/50-default.conf
Output from tail -f /var/log/syslog
Output from /var/log/telegraf/telegraf.log
No other messages are in the telegraf log other than the initial start up messages. Data is being written, so i know the plugin works in that respect. Although the server time is out by an hour. If there's anything else i can provide please let me know. Apologies for the lack of availability to upload the conf files and link to them. Phil |
I've finally been able to reproduce this. I noticed no network traffic occurring at the time the log gets generated and after closer inspection of your |
is this issue fixed? I am seeing same errors in latest version of telegraf(1.7.2). I am trying to send my docker daemon logs via syslog drivers. 018/07/27 16:09:10 I! Using config file: /etc/telegraf/telegraf.conf Here is my docker daemon json config: { |
This issue is not fixed. I experience the exact same error as @mthota15 |
@turbo if you don't mind continuing this in 4482, that better describes your issue, thanks. |
Relevant telegraf.conf:
System info:
Ubuntu 16.04.3 x64 Telegraf 1.7
Steps to reproduce:
Install the latest Telegraf build
Followed this topic and read me
Restart Telegraf after editing the config and wait for the data, tail the telegraf logs
Expected behavior:
Collect mertics from Syslog and send them to InfluxDB
Actual behavior:
Telegraf does send the data to InfluxDB but this error appears in the telegaf log:
2018-06-22T11:19:49Z E! Error in plugin [inputs.syslog]: found EOF, expecting a MSGLEN 2018-06-22T11:19:59Z E! Error in plugin [inputs.syslog]: found EOF, expecting a MSGLEN 2018-06-22T11:20:09Z E! Error in plugin [inputs.syslog]: found EOF, expecting a MSGLEN 2018-06-22T11:20:19Z E! Error in plugin [inputs.syslog]: found EOF, expecting a MSGLEN 2018-06-22T11:20:29Z E! Error in plugin [inputs.syslog]: found EOF, expecting a MSGLEN 2018-06-22T11:20:39Z E! Error in plugin [inputs.syslog]: found EOF, expecting a MSGLEN 2018-06-22T11:20:49Z E! Error in plugin [inputs.syslog]: found EOF, expecting a MSGLEN 2018-06-22T11:20:59Z E! Error in plugin [inputs.syslog]: found EOF, expecting a MSGLEN 2018-06-22T11:21:02Z E! Error in plugin [inputs.syslog]: found EOF, expecting a MSGLEN 2018-06-22T11:21:09Z E! Error in plugin [inputs.syslog]: found EOF, expecting a MSGLEN
Additional info:
I think my config is valid, Telegraf starts with no issues and sends the metrics to InfluxDB. I've also tested this with a separate Telegraf instance sending data to a remote InfluxDB.
If i can provide anything else let me know.
Regards,
PhilB
The text was updated successfully, but these errors were encountered: