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

Radio inputs routing to different AMQP queues or topic exchanges ? #536

Closed
henrikjohansen opened this issue May 6, 2014 · 1 comment
Closed
Labels

Comments

@henrikjohansen
Copy link

According to #385 it should be possible to let inputs route to different AMQP queues or topic exchanges (just like the first invocation of graylog2-radio, see @lennartkoopmann comment on the referenced issue) ... but it does not look like that is possible with 0.20.2-rc1?

We have a lot of stuff that needs pre-processing before it gets ingested by our server nodes and this feature would allow us to do so rather elegantly (radios receives data, push that to pre-process queues, something does something to the messages in those queues and inserts the processed messages into a queue that our server nodes ingest).

The above has the definite benefit of allowing us to concentrate our redundancy and availability efforts towards our radio nodes (to make sure that we do not loose events) ... right now we have to duplicate this to the other tools that are needed in our toolchain which is rather inefficient ...

@kroepke kroepke added the inputs label May 27, 2014
@bernd
Copy link
Member

bernd commented Feb 27, 2015

Closing this because radio has been deprecated as of v1.0.0. Please re-open this is still an issue. Thank you!

@bernd bernd closed this as completed Feb 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants