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

Support Excluding Queues in RabbitMQ Plugin (Feature Request) #2214

Closed
evanccnyc opened this issue Dec 30, 2016 · 7 comments
Closed

Support Excluding Queues in RabbitMQ Plugin (Feature Request) #2214

evanccnyc opened this issue Dec 30, 2016 · 7 comments
Milestone

Comments

@evanccnyc
Copy link

evanccnyc commented Dec 30, 2016

Proposal:

The RabbitMQ plugin should support excluding queues based on name. This needed because rabbitmq supports the creation of temporary queues see RabbitMQ documentation here (scroll down to Temporary Queues). This is really important because otherwise you can end up with thousands of data points for queues that exist for very short amount of time (seconds).

It is also worth noting that Diamond has support for this under queues_ignored

Current behavior:

No ability to ignore queues.

Desired behavior:

In the config file something like this should be allowed:

[[inputs.rabbitmq]]
  ignore_queues = amq.gen-*

And those queues are not retrieved by telegraf.

Use case:

As stated above, when using temporary queues, you can end up with thousands of data points very quickly for queues that disappear in seconds. This clogs up any metric database you are using.

@phemmer
Copy link
Contributor

phemmer commented Jan 1, 2017

You can do this with:

[[inputs.rabbitmq]]
  [inputs.rabbitmq.tagdrop]
    queue = ["amq.gen-*"]

@evanccnyc
Copy link
Author

@phemmer

Ah thanks didnt see that documented anywhere.

@phemmer
Copy link
Contributor

phemmer commented Jan 5, 2017

@sparrc
Copy link
Contributor

sparrc commented Jan 9, 2017

that's a decent workaround, but we should also probably support an option that specifically avoids collecting the data in the first place, since there is an overhead to using drop options.

@sparrc sparrc added this to the Future Milestone milestone Jan 11, 2017
@danielnelson danielnelson removed this from the Future Milestone milestone Jun 14, 2017
@botzill
Copy link

botzill commented Nov 3, 2017

Can we exclude randomly generated queues names like: 450ec2647db4465482ee16c4794d664a ?

Why don't we allow regexp for things like tagdrop?

@danielnelson
Copy link
Contributor

@botzill Might be tricky, you could try something like tagpass = "{[0-9],[a-f]}{[0-9],[a-f]}*". This would only test the first two letters though, so you might have to extend it a bit.

I'm open to adding regex support for the measurment filtering. Check this comment for some ideas on how we could do this: #2726 (comment)

@danielnelson
Copy link
Contributor

Closed in #3702

@danielnelson danielnelson added this to the 1.6.0 milestone Jan 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants