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

Raw AMQP not creating exchange binding #1599

Closed
rikatz opened this issue Dec 2, 2015 · 3 comments
Closed

Raw AMQP not creating exchange binding #1599

rikatz opened this issue Dec 2, 2015 · 3 comments
Assignees
Labels
bug
Milestone

Comments

@rikatz
Copy link

@rikatz rikatz commented Dec 2, 2015

Starting some tests with RabbitMQ + Graylog, after creating a raw/plaintext AMQP input I've noticed that Graylog doesn't create the exchange => queue binding.

It creates the queue succesfully, but the queue has empty bindings, shown on the attached images.

glogos1
glogos2
glogos3

EDIT: This way, I do have to manually bind the exchange with the log queue.
Forgot to mention, I'm using Graylog Server 1.2.2.

@bernd bernd added the bug label Dec 15, 2015
@bernd bernd added this to the 1.3.1 milestone Dec 15, 2015
bernd added a commit that referenced this issue Dec 15, 2015
This was missing before and the exchange and routing-key options were
not used.

The binding option defaults to "false" to avoid existing setups to fail
when the given exchange (there is a default) does not exist.

Fixes #1599
@bernd
Copy link
Member

@bernd bernd commented Dec 15, 2015

@rikatz Thank you for the report! We created a PR in #1633 to fix this.

@bernd bernd self-assigned this Dec 15, 2015
bernd added a commit that referenced this issue Dec 15, 2015
This was missing before and the exchange and routing-key options were
not used.

The binding option defaults to "false" to avoid existing setups to fail
when the given exchange (there is a default) does not exist.

Fixes #1599
@bernd bernd closed this in 1dfd986 Dec 15, 2015
@bernd
Copy link
Member

@bernd bernd commented Dec 15, 2015

@rikatz This will be fixed in the upcoming Graylog 1.3.1.

@rikatz
Copy link
Author

@rikatz rikatz commented Dec 15, 2015

Great \o/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants