At present, the logging mechanism for Node-RED projects directs all logs to the 'driver', which can be accessed through the FlowFuse Project logs interface. In environments where Kubernetes clusters are deployed and are integrated with monitoring solutions (such as log forwarding to OTEL/ FluentBit for pods, and then to traces/metrics/etc. to backends like Prometheus/Jaeger/, etc.), there is a valuable opportunity to streamline monitoring practices.
Enabling Node-RED projects to output their logs directly to the pod's console will facilitate a more unified approach to monitoring by leveraging existing log aggregation configurations.
Description
At present, the logging mechanism for Node-RED projects directs all logs to the 'driver', which can be accessed through the FlowFuse Project logs interface. In environments where Kubernetes clusters are deployed and are integrated with monitoring solutions (such as log forwarding to OTEL/ FluentBit for pods, and then to traces/metrics/etc. to backends like Prometheus/Jaeger/, etc.), there is a valuable opportunity to streamline monitoring practices.
Enabling Node-RED projects to output their logs directly to the pod's console will facilitate a more unified approach to monitoring by leveraging existing log aggregation configurations.