From a8e7c7092388510927b7115a43f1d61545d89bf5 Mon Sep 17 00:00:00 2001
From: Tawakalt <olaniyitaiwo95@yahoo.com>
Date: Wed, 19 Jul 2023 11:37:06 +0200
Subject: [PATCH 1/3] update docs

---
 docs/docs/event-brokers.mdx | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/docs/event-brokers.mdx b/docs/docs/event-brokers.mdx
index c1a23b1bf5a5..f53224dac42e 100644
--- a/docs/docs/event-brokers.mdx
+++ b/docs/docs/event-brokers.mdx
@@ -112,6 +112,11 @@ if __name__ == "__main__":
     channel.start_consuming()
 ```
 
+### Sending Events to Multiple Queues
+
+You can specify multiple event queues to publish events to.
+This should work for all event brokers supported by Pika (e.g. RabbitMQ)
+
 ## Kafka Event Broker
 
 While RabbitMQ is the default event broker, it is possible to use [Kafka](https://kafka.apache.org/) as the main broker for your
@@ -190,6 +195,14 @@ If using the `SASL_SSL` protocol, the endpoints file should look like:
 ```yaml-rasa (docs/sources/data/test_endpoints/event_brokers/kafka_sasl_ssl_endpoint.yml)
 ```
 
+### Sending Events to Multiple Queues
+
+Kafka does not allow you to configure multiple topics. 
+
+However, multiple consumers can read from the same queue as long as they are in different consumer groups.
+Each consumer group will process all events independent of each other 
+(in a sense, each group has their own reference to the last event they have processed).
+
 ## SQL Event Broker
 
 It is possible to use an SQL database as an event broker. Connections to databases are established using

From cc7704c10df74f3e6a22811ab3f5ad8b915a6b7d Mon Sep 17 00:00:00 2001
From: Tawakalt <olaniyitaiwo95@yahoo.com>
Date: Wed, 19 Jul 2023 11:51:00 +0200
Subject: [PATCH 2/3] add changelog entry

---
 changelog/12677.doc.md | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 changelog/12677.doc.md

diff --git a/changelog/12677.doc.md b/changelog/12677.doc.md
new file mode 100644
index 000000000000..383270b5a476
--- /dev/null
+++ b/changelog/12677.doc.md
@@ -0,0 +1 @@
+Updated docs on sending Conversation Events to Multiple DBs.
\ No newline at end of file

From 5a86e067b835bbc5494a749d9b80e7a8a93c1538 Mon Sep 17 00:00:00 2001
From: Tawakalt <olaniyitaiwo95@yahoo.com>
Date: Wed, 19 Jul 2023 16:47:58 +0200
Subject: [PATCH 3/3] add link to docs

---
 docs/docs/event-brokers.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/event-brokers.mdx b/docs/docs/event-brokers.mdx
index f53224dac42e..73fb1afa9786 100644
--- a/docs/docs/event-brokers.mdx
+++ b/docs/docs/event-brokers.mdx
@@ -201,7 +201,7 @@ Kafka does not allow you to configure multiple topics.
 
 However, multiple consumers can read from the same queue as long as they are in different consumer groups.
 Each consumer group will process all events independent of each other 
-(in a sense, each group has their own reference to the last event they have processed).
+(in a sense, each group has their own reference to the last event they have processed). [Kafka: The Definitive Guide](https://www.oreilly.com/library/view/kafka-the-definitive/9781491936153/ch04.html#:~:text=Kafka%20consumers%20are%20typically%20part,the%20partitions%20in%20the%20topic.)
 
 ## SQL Event Broker