Is the :arguments option actually used in the plugin?

[ifoo]

I was currently testing the arguments option of the rabbitmq output plugin.

Specifically, i tried the 'x-max-length' option like this:

rabbitmq {
...
arguments => { "x-max-length" => 10000 }
...
}

But after checking in the rabbitmq management interface the option doesn't seem to be honored. A quick check at the source code (https://github.com/logstash-plugins/logstash-output-rabbitmq/blob/master/lib/logstash/outputs/rabbitmq.rb and https://github.com/logstash-plugins/logstash-mixin-rabbitmq_connection/blob/master/lib/logstash/plugin_mixins/rabbitmq_connection.rb) suggests, that the :argument option is not used in the code, or did I miss anything?

[sxmichael]

i was also curious about it. arguments and passive options are queue-specific, though no queue name could be provided and no queue-specific logic exists not in output nor in plugin. from the history, it seems that both options was created on initial commit of the mixin (https://github.com/logstash-plugins/logstash-mixin-rabbitmq_connection/pull/1/files#diff-5a4e6da9864c64f906837378a6f551e6R56) which was "Pulled from the rabbitmq output sources. Modified to be a mixin." by @andrewvc , though no such logic nor option itself was not present in the original output... (relevant commit: bea6ebf)

Those options are used though in logstash-input-plugin...

[andrewvc]

Apologies here, this seems to have just been an artifact of that being legacy code. I'll try and take a look at it this week.

[Woudan]

Is there a fix in progress for this issue?

[Ricaz]

This is turning into a long week..