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

execd processor does not handle newline characters in strings #8095

Closed
M0rdecay opened this issue Sep 8, 2020 · 1 comment · Fixed by #8499
Closed

execd processor does not handle newline characters in strings #8095

M0rdecay opened this issue Sep 8, 2020 · 1 comment · Fixed by #8499
Assignees
Labels
bug unexpected problem or unintended behavior good first issue This is a smaller issue suited for getting started in Telegraf, Golang, and contributing to OSS.

Comments

@M0rdecay
Copy link
Contributor

M0rdecay commented Sep 8, 2020

Actual behavior:

If the external processor returns data in the influxdb format in several lines, a parsing error occurs:

2020-09-08T12:00:39Z E! [processors.execd] Parse error: metric parse error: expected tag at 1:65: "some data here"

Additional info:

The situation is well described here - #7461
But now it occurs in the execd processor

@M0rdecay M0rdecay added the bug unexpected problem or unintended behavior label Sep 8, 2020
@ssoroka
Copy link
Contributor

ssoroka commented Sep 8, 2020

Should be easy enough to resolve. Will take a look at it

@stephanie-engel stephanie-engel added the good first issue This is a smaller issue suited for getting started in Telegraf, Golang, and contributing to OSS. label Nov 9, 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 good first issue This is a smaller issue suited for getting started in Telegraf, Golang, and contributing to OSS.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants