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

RabbitMQ connections causes cardinality explosion #2168

Closed
phemmer opened this issue Dec 15, 2016 · 1 comment · Fixed by #2169
Closed

RabbitMQ connections causes cardinality explosion #2168

phemmer opened this issue Dec 15, 2016 · 1 comment · Fixed by #2169
Assignees

Comments

@phemmer
Copy link
Contributor

phemmer commented Dec 15, 2016

Directions

Bug report

Relevant telegraf.conf:

[[inputs.rabbitmq]]
  url = "http://localhost:15672"

System info:

Telegraf master (17b307a)
CentOS/7

Steps to reproduce:

  1. Start telegraf

Expected behavior:

Telegraf output should contain a relatively stable number of series.

Actual behavior:

Telegraf outputs a new series every time a client connects to RabbitMQ because it has a tag called connection which contains the TCP tuple (client-ip + client-port + server-ip + server-port)

Additional info:

Change introduced by #1908

@sparrc
Copy link
Contributor

sparrc commented Dec 15, 2016

sigh, I'll revert #1908

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

Successfully merging a pull request may close this issue.

3 participants