Use MQTT broker to retrieve events

This configuration leverages the flow runtime’s internal MQTT broker to retrieve flow/module status event changes. Create an event-driven notification architecture with requiring external monitoring tools.

• Similar to the HTTP approach, either connect to the flow runtime’s local broker from an external MQTT client, or create a flow which subscribes to the relevant topics to send out event notifications.

• The flow runtime publishes event-triggered messages to subscribed partners. The root topic for all the messages will be $aveva/.

• For example $aveva/flows/{flowDefinitionId}/started publishes when a flow starts.

The $aveva/ topic cannot be published; only subscriptions are allowed. If a client tries to publish with a topic that starts with $aveva/, the client is disconnected.

Note: MQTT Notifications are disabled for remote sessions. Only deployed flows trigger MQTT notifications.