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

Consul input plugin with InfluxDB output - multiple checks per service #1825

Closed
bondido opened this issue Sep 29, 2016 · 2 comments
Closed
Labels
bug unexpected problem or unintended behavior
Milestone

Comments

@bondido
Copy link

bondido commented Sep 29, 2016

Bug report

Consul input plugin with InfluxDB output doesn't report all data in case of collecting data from service with more than one check configured. Status from only one (randomly choosed per probe/timestamp) check is written to influxdb database.
Also, if any service is in maintenance mode (which is in fact temporarily configured 'critical' check on this service), this information is not always written to influxdb.

System info:

[Include Telegraf version, operating system name, and other relevant details]
Telegraf - version 1.0.0
InfluxDB - version 0.13.0
Consul - version 0.6.4
OS: Ubuntu 14.04.5 LTS

Steps to reproduce:

  1. Configure telegraf with Consul input and InfluxDB output plugin.
  2. Monitor consul service with more than one check defined.

Expected behavior:

Write consul service's all checks status in InfluxDB.

Actual behavior:

Write status of only one check per service per probe/timestamp in InfluxDB.

@harnash
Copy link
Contributor

harnash commented Oct 30, 2016

@bondido thanks for report. I'll look into it and hopefully fix it this week.

@sparrc sparrc added the bug unexpected problem or unintended behavior label Nov 2, 2016
@sparrc sparrc added this to the Future Milestone milestone Nov 2, 2016
@sparrc sparrc modified the milestones: 1.2.0, Future Milestone Nov 4, 2016
@sparrc
Copy link
Contributor

sparrc commented Dec 20, 2016

closed by #1994

@sparrc sparrc closed this as completed Dec 20, 2016
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

No branches or pull requests

3 participants