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

Unexpected output from the printer processor #4416

Closed
voiprodrigo opened this issue Jul 12, 2018 · 4 comments · Fixed by #4417
Closed

Unexpected output from the printer processor #4416

voiprodrigo opened this issue Jul 12, 2018 · 4 comments · Fixed by #4417
Labels
bug unexpected problem or unintended behavior
Milestone

Comments

@voiprodrigo
Copy link
Contributor

Running 1.7.0 on CentOS 7.

When I activate the printer processor, journalctl shows me lines like this:

Jul 12 16:50:06 xxxxx telegraf[25525]: [66 117 114 ... 10]

I doubt this is the expected behaviour..

Thanks.

@danielnelson danielnelson added this to the 1.7.2 milestone Jul 12, 2018
@danielnelson danielnelson added the bug unexpected problem or unintended behavior label Jul 12, 2018
@danielnelson
Copy link
Contributor

Thanks for the report, as a workaround you can probably use the file output instead.

@voiprodrigo
Copy link
Contributor Author

Thanks for the report, as a workaround you can probably use the file output instead.

@danielnelson indeed, file served my purpose just fine, which was quick debug, and even better for not clogging service logs.

Sent with GitHawk

@voiprodrigo
Copy link
Contributor Author

By the way, I noticed that using namepass defined with a simple string instead of array, caused some really weird behavior. I was using it with processor override + name_override and it renamed lots of measurements that it shouldn’t until I noticed the mistake. And shouldn’t the type of namepass be enforced? Is this known, or should I open a new issue?

Sent with GitHawk

@danielnelson
Copy link
Contributor

Sounds similar to #3444, but can you open a new issue?

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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants