FlowFuse
Observability Integrations
Description
When FlowFuse is a part of a larger ecosystem, companies tend to have centralised monitoring tools. It has been mentioned that there would be considerable value in us offering integrations such that FlowFuse and Node-RED instances could be monitored in such external tooling.
Related Issues/Epics
- https://github.com/FlowFuse/flowfuse/issues/223
Requested By
- https://app-eu1.hubspot.com/contacts/26586079/record/0-2/13089944531
Which customers would this be available to
Enterprise Tier Only (EE)
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
@ppawlowski Do you have insight as to which external tools customers might use for this?
@ppawlowski Do you have insight as to which external tools customers might use for this?
For self-hosted most widely used approach is Prometheus + Grafana. As for enterprise solutions, Datadog or Dynatrace are the top choices IMO. The set of tools doesn't matter because the approach for all of them is most likely the same - collect application metrics from some endpoint, send them to some timeseries database and present via some graphical interface. The main goal here is to expose such an endpoint with metrics. AFAIK, for Node-RED flows, this is doable with node-red-contrib-prometheus-exporter.
We have an existing prometeus exporter loaded as a plugin for node-red by the NR launcher
If I'm reading this correctly, we already have a way of providing this value, and the issue can be closed. @ppawlowski Can you confirm this?
There are two Node-RED nodes that I am aware of and that are capable of providing metrics/traces for flows:
Since every flow is unique, I don't think there is a possibility of providing a generic observability that can be applied to every flow. Every Node-RED flow developer needs to use one og the nodes I mentioned to expose metrics/traces they want to observe. The "Monitoring and Optimizing Node-RED Flows with Open Telemetry" blog post might be helpful as well.
Thanks @ppawlowski . Since this is an enablement issue and not a product need, I'm closing this.
@Esmewieringa Since this was a customer request, please reach out to the customer and ask if they need help implementing the solution that Piotr described.
