> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/guides/system-connectivity/messaging-event-streaming.md).

# Messaging & Event Streaming

Integration guides for message brokers and event streaming platforms such as Apache Kafka, RabbitMQ, and HiveMQ.

These guides describe how to stream shop floor data between Connectware and message brokers or event streaming platforms. The following guides are available:

| Guide                                                                                                           | Connector                                                 | Description                                                       |
| --------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | ----------------------------------------------------------------- |
| [Apache Kafka](/2-6-1/guides/system-connectivity/messaging-event-streaming/apache-kafka-integration.md)         | [Kafka](/2-6-1/connectors/enterprise-connectors/kafka.md) | Produce to and consume from a self-managed Kafka cluster.         |
| [Confluent Cloud](/2-6-1/guides/system-connectivity/messaging-event-streaming/confluent-cloud-integration.md)   | [Kafka](/2-6-1/connectors/enterprise-connectors/kafka.md) | Produce and consume with SASL API key authentication.             |
| [Redpanda](/2-6-1/guides/system-connectivity/messaging-event-streaming/redpanda-integration.md)                 | [Kafka](/2-6-1/connectors/enterprise-connectors/kafka.md) | Produce and consume on self-hosted clusters and Redpanda Cloud.   |
| [Azure Event Hubs](/2-6-1/guides/system-connectivity/messaging-event-streaming/azure-event-hubs-integration.md) | [Kafka](/2-6-1/connectors/enterprise-connectors/kafka.md) | Stream data through the Kafka endpoint of Event Hubs.             |
| [RabbitMQ](/2-6-1/guides/system-connectivity/messaging-event-streaming/rabbitmq-integration.md)                 | [MQTT](/2-6-1/connectors/enterprise-connectors/mqtt.md)   | Bridge MQTT and AMQP through the RabbitMQ MQTT plugin.            |
| [HiveMQ](/2-6-1/guides/system-connectivity/messaging-event-streaming/hivemq-integration.md)                     | [MQTT](/2-6-1/connectors/enterprise-connectors/mqtt.md)   | Bridge shop floor data to HiveMQ Cloud or a self-hosted platform. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/guides/system-connectivity/messaging-event-streaming.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.