# Don't binding name index on Elasticsearch when using RabbitMQ

**URL:** <https://discuss.elastic.co/t/dont-binding-name-index-on-elasticsearch-when-using-rabbitmq/37971>\
**Category:** Logstash\
**Created:** [December 25, 2015, 10:41am UTC](https://discuss.elastic.co/t/dont-binding-name-index-on-elasticsearch-when-using-rabbitmq/37971 "2015-12-25T10:41:10Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [December 28, 2015, 8:28am UTC](https://discuss.elastic.co/t/dont-binding-name-index-on-elasticsearch-when-using-rabbitmq/37971/6 "2015-12-28T08:28:54Z")

</div>

Hi,

see [this response](https://discuss.elastic.co/t/beats-deployment-with-logstash-relays-to-a-central-ls-instance/36107/4?u=steffens) for workaround. Problem is the '@metadata' field is not exported in output plugins.

---

_[View the full topic](https://discuss.elastic.co/t/dont-binding-name-index-on-elasticsearch-when-using-rabbitmq/37971)._