n8n-observability

To add observability to n8n workflows, you propagate a correlation_id end-to-end and enable structured logging with context like workflow_name, execution_id, and node_name. This provides end-to-end tracing across API, DB, ERP, and messaging integrations to improve reliability.

For n8n workflow operability, track execution_success_total, execution_error_total, execution_duration_ms, retry_count_total, external_api_latency_ms, and external_api_429_total. These base metrics enable actionable alerts and reduce mean time to resolution.

Correlation IDs help debug n8n production workflows by providing logical traceability across executions and integrations. Propagating a correlation_id end-to-end links structured logs across multiple systems like APIs, databases, and ERPs to reduce MTTR during degradations.

Yes, n8n workflow observability supports actionable alerting with thresholds and runbooks. These alerts trigger on sustained degradations or critical errors, guiding operators through resolution to maintain production workflow reliability.

Yes, you can monitor external API latency in n8n integrations by capturing the external_api_latency_ms metric. This tracks response times across integrated systems and pairs with external_api_429_total to detect rate limiting issues.