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

Tailing files stopped working since v1.15 #7880

Closed
Tenzer opened this issue Jul 23, 2020 · 4 comments · Fixed by #7927
Closed

Tailing files stopped working since v1.15 #7880

Tenzer opened this issue Jul 23, 2020 · 4 comments · Fixed by #7927
Labels
bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Milestone

Comments

@Tenzer
Copy link
Contributor

Tenzer commented Jul 23, 2020

I've upgraded from Telegraf v1.14 to v1.15.1 in our systems today and found that it broke one of our use cases.

We are tailing some log-like files from a service, the service outputs lines in InfluxDB format which is then read by Telegraf and passed on to our metrics system. I made a minimal example of this:

telegraf.conf

[[inputs.tail]]
  files = ["clock.log"]
  data_format = "influx"

[[processors.printer]]

[[outputs.discard]]

I've then run this loop in bash in order to write to clock.log:

while :; do
    echo "clock now=$(date +%s)"
    sleep 1
done >> clock.log

Using that example I was able to use Git bisect which pointed at this stopping working when #7792 was merged.

I've tried to set character_encoding in the config file to both an empty string and "utf-8" but it doesn't seem to make any difference, so I think the problem might more deeply rooted.

@9point6
Copy link

9point6 commented Jul 23, 2020

We've also had a similar issue with inputs.tail. Validated that locking to < 1.15.0 has mitigated the issue for us

@danielnelson danielnelson added bug unexpected problem or unintended behavior regression something that used to work, but is now broken labels Jul 23, 2020
@danielnelson danielnelson pinned this issue Jul 23, 2020
@danielnelson danielnelson added this to the 1.15.2 milestone Jul 23, 2020
@danielnelson
Copy link
Contributor

Can everyone affected try out one of these builds with the proposed fix and let us know if it resolves the issue?

@Tenzer
Copy link
Contributor Author

Tenzer commented Jul 24, 2020

@danielnelson Thanks, I can confirm it fixes the problem for me.

@philipptrenz
Copy link

I can also confirm that this fixes the issue, thanks! 👌🏼

@ssoroka ssoroka unpinned this issue Aug 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Projects
None yet
4 participants