cannot use an exchange with specific properties

[balooka]

Please post all product and debugging questions on our forum. Your questions will reach our wider community members there, and if we confirm that there is a bug, then we can open a new issue here.

For all general issues, please provide the following details for fast resolution:

• Version: 4.0.11
• Operating System: Linux - CentOS

Issue description: Plugin doesn't work for exchange with parameters (for example alternate-exchange)

The current configuration supports the following two parameters:

• arguments
• passive

Both of these only refer to the queue configuration, but not the exchange configuration.

In my case, I have defined an alternate exchange in my (direct) exchange configuration,
this to ensure that even in the case of unexpected messages routing key, the messages are not lost.
Because arguments cannot be provided for the exchange in the configuration, and passive option is not available for the exchange either, this means that the logstash instance will fail to start properly because it's confronting it's configuration with the existing one and it doesn't match.

The plugin should be updated to either allow for the passive option to also apply to the exchange,
or to support exchange arguments.

[gbroten-diitalk]

I've encountered the exact same problem. I have configured rabbitmq to support alternate exchanges, but logstash doesn't support arguments on exchanges. FYI, this only becomes apparent by looking at the logstash rabbitmq plugin code, the logstash documentation specifies that is does:https://www.elastic.co/guide/en/logstash/current/plugins-outputs-rabbitmq.html#plugins-outputs-rabbitmq-arguments

[vanbcguy]

This affects me too... I can't use RabbitMQ to route messages as I can't specify an alternate-exchange the way things are currently written.