n8n Monitoring with OpenTelemetry and OpenObserve

Monitoring n8n workflows in production requires additional external metrics, alerting, and cross-workflow correlation beyond what is provided by the built-in execution UI. Self-hosted n8n can expose Prometheus metrics by setting an environment variable, while OpenTelemetry (OTel) trace export necessitates a custom Docker image with a tracing bootstrap file. An OTel Collector is used to bridge n8n and OpenObserve, handling both Prometheus metrics and OTLP traces. OpenObserve offers an integration guide for n8n, covering both Prometheus metrics and webhook instrumentation paths. In production, n8n's UI is limited for query capabilities, and alerting on failure rates or cross-workflow analyses is not feasible. Utilizing a combination of Prometheus metrics and OTel traces, users can achieve full-stack observability akin to other services. For self-hosted instances, enabling metrics requires setting specific environment variables, while traces need a customized Docker setup. OpenObserve's integration guide outlines the setup for both metrics and traces, ensuring comprehensive monitoring.