# Log Conversations - 2nd Event Broker

**URL:** https://forum.rasa.com/t/log-conversations-2nd-event-broker/19937
**Category:** \[Deprecated\] Rasa X Community Edition
**Created:** [October 17, 2019, 6:17am UTC](https://forum.rasa.com/t/log-conversations-2nd-event-broker/19937 "2019-10-17T06:17:24Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![wladneto](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/wladneto/32/5151_2.png) [@wladneto](https://forum.rasa.com/u/wladneto)
#### Post date: [July 6, 2021, 12:34pm UTC](https://forum.rasa.com/t/log-conversations-2nd-event-broker/19937/10 "2021-07-06T12:34:43Z")

</div>

Hello @stephens yes i looked! thanks… So…my solution was use the endpoints.yml to create some queues rabbitMQ (pika)… and after i created a consumer to get events in a queue and finnaly send to my another aplication… in my case i sent my events to [dashbot.io](http://dashbot.io) and sent to kafka by another queue too

I suggest that endpoints.yaml accepts more than one broker…That way we can easily connect to other integrations already created via broker.

---

_[View the full topic](https://forum.rasa.com/t/log-conversations-2nd-event-broker/19937)._