Push events

Another way to consume the flow runtime API is to create a flow that uses the API. Use the HTTP Request module to call the API and extract the relevant information. This uses event triggers to send notifications to external brokers, APIs, HTTP endpoints, or notifying a user with the information.

This configuration pushes event data to external systems, which is useful when a monitoring solution does not have access to the flow runtime's local API, but the monitoring system's endpoint is instead exposed. CONNECT flows uses the HTTP Request module to push data to the customer's endpoint. This functionality works on the same flow runtime alongside other flows.

Contingency consideration and workaround

The risk of this type of implementation is if the entire flow runtime fails, the monitoring flow in that runtime will also fail. As a potential workaround, configure a dedicated monitoring flow runtime to only run monitoring flows in a dedicated environment.

This setup bridges network gaps between the flow runtime (production network) and monitoring system (office network/cloud).