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
Exec plugin generating duplicate measurements #1373
Comments
I'm currently using the version 1.0.0-beta1 but It happened on the previous version as well. |
Can you be more specific? What is the exec plugin executing? What metrics is the script generating?your config file? provide the script? output of the script that is being executed? |
It is executing an script made by us. Anyway and in order to avoid any doubt, I tried to send the output to a text file and I changed the configs to just read this file, the results were the same though. See configs below:
The content was a variation, 50 lines to be precise, of:
Just to add more information, the product name normally has spaces but I'm escaping all of them, like so:
|
@rafaelabdo can you provide actual metrics that reproduce the issue? Unforunately there's not much I can do without reproducing it. |
Ok, see it below: Config:
Content:
Tests:
|
can you provide your influxdb output config? |
Yes:
|
Is there anything else that could be helpful to reproduce this issue? |
I haven't had the chance to try to reproduce yet, please be patient, or submit a PR ;-) |
for my own debugging purposes, I got 50 points, 50 points, then 52 points:
|
as far as I can tell this is not a telegraf issue, I wrote up a script for writing this data to InfluxDB using curl -XPOST 'http://localhost:8086/write?db=telegraf' --data-binary '@/tmp/example.txt'
curl -G --silent 'http://localhost:8086/query' --data-urlencode "q=SELECT count(orders) FROM antixxxx" --data-urlencode "db=telegraf" # | jq '.results[0].series[0].values[0][1]'
curl -XPOST --silent 'http://localhost:8086/query' --data-urlencode "q=DROP MEASUREMENT antixxxx" --data-urlencode "db=telegraf" > /dev/null (delete the comment on the 2nd line if you have |
AFAICT this is an influxdb bug, possibly related to dropping measurements, see influxdata/influxdb#7039 |
@rafaelabdo you hit a very interesting corner case with the metrics you were writing, which was a bug in InfluxDB. This PR: influxdata/influxdb#7027 fixed it, and it was merged just after version 1.0.0-beta3 was released. So the fix will be for the DB, and it will be ready in version 1.0 (or beta4, whichever comes first). |
I guess that I'm facing the same problem with "inputs_exec" as described here: #773
Some tips for this issue:
The text was updated successfully, but these errors were encountered: