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

Unable to parse: invalid boolean when sending data from fluentd #2547

Closed
xuoguoto opened this issue May 8, 2021 · 2 comments
Closed

Unable to parse: invalid boolean when sending data from fluentd #2547

xuoguoto opened this issue May 8, 2021 · 2 comments

Comments

@xuoguoto
Copy link

xuoguoto commented May 8, 2021

I am sending some metrics from fluentd to Kapacitor OSS version 1.5.9 for stream processing. Using fangli/fluent-plugin-influxdb as the fluentd plugin to send data to Kapacitor in version 1 lineformat.

From the packet capture I can see that , this is the line thats being sent to Kapacitor:

nodeexporter09,_seq=6 host={"network"=>{"out"=>{"bytes"=>1329771, "packets"=>457},
 "in"=>{"bytes"=>1309413, "packets"=>461}}, "name"=>"myhost"} 1620454532615

Which gets the error: unable to parse: invalid boolean

Fluentd sends multiple points in a single HTTP request, and all of them are rejected by Kapacitor with same error message.

My questions are:

  1. Is this a valid line in line protocol? I could't find its definition in reference docs, esp the usage of {} and _seq?
  2. If so, what could be the error here

Any update on Kapacitor supporting Influx2.0 line protocol. I am successfully able to send data from fluentd to InfluxDB2.0, but since InfluxDB2.0 do not support streaming, I have to send a copy of data to Kapacitor too.

@xuoguoto
Copy link
Author

xuoguoto commented May 9, 2021

This was a problem with fluent-plugin-influxdb. Fixed and submitted a PR at fangli/fluent-plugin-influxdb#107.

This issue can be closed.

@xuoguoto
Copy link
Author

xuoguoto commented May 9, 2021

It would be interested to know when or if Kapacitor can handle Influx2.0 line protocol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant