Telemetry & Observability
Relevant source files
The following files were used as context for generating this wiki page:
Telemetry and observability within n8n encompass the collection of usage metrics, event tracking, performance benchmarking, and system monitoring. The system tracks internal events for development insights, provides an event bus for enterprise logging, and implements performance monitoring to detect regressions in the frontend and backend.
Telemetry Systems
n8n implements multiple telemetry layers to capture development metrics and product usage data.
Event Registry
The telemetry registry tracks registered events, their names, descriptions, and properties. You view the catalog of registered telemetry events by running the command pnpm --filter @n8n/telemetry catalog. If an event does not appear in the catalog, search the codebase for direct call sites as the registry is adopted incrementally.
Sources: AGENTS.md:31-34
Anonymous Development Metrics
The project records anonymous development metrics via scripts/dev-metrics. This system captures pnpm command arguments to understand developer workflows. To protect sensitive data, the system drops arguments following secret-carrying keywords such as config, login, publish, and token. It also strips the home directory from file paths.
Sources: AGENTS.md:23-28
Event Bus and Syslog
For enterprise environments, n8n provides an event bus that integrates with syslog via TCP or UDP. This allows for external logging and monitoring of internal n8n events.
Sources: CONTRIBUTING.md:348-350
Performance Observability
The performance toolkit measures and asserts system behavior during development and testing to prevent regressions.
Performance Benchmarking
The system measures specific action durations, such as opening nodes or executing workflows, using the Playwright performance toolkit. It calculates metrics including:
- Cold load duration: Time taken for the initial page load.
- Server/Browser Heap: Memory usage on both the backend and the client renderer.
- DOM Node Count: The number of elements rendered in the browser.
- Re-render counts: Tracking Vue component updates to detect reactivity issues.
Sources: packages/quality/testing/playwright/tests/performance/README.md:123-132, packages/quality/testing/playwright/tests/performance/README.md:144-152
Performance Tiers
Benchmarks are categorized into tiers to simulate different workflow complexities:
| Tier | Node Count | Use Case |
|---|---|---|
| S | 30 | Typical user workflow |
| M | 80 | Large customer automation |
| L | 200 | Power-user / orchestration |
| Sources: packages/quality/testing/playwright/tests/performance/README.md:107-111 |
Sentinel Regression Detection
A sentinel script (scripts/canvas-perf-sentinels.mjs) parses test results and fails jobs if metrics exceed defined thresholds, such as a cold load exceeding 30 seconds at Tier M or pan p95 frame times exceeding 100ms.
Sources: packages/quality/testing/playwright/tests/performance/README.md:172-183
Workflow Monitoring and Health Checks
Monitoring best practices ensure that automated workflows remain healthy and provide alerts upon failure.
Error Handling Architecture
Reliable monitoring requires the "Continue On Fail" or "Never Error" mode on check nodes to ensure the workflow proceeds to alerting logic even when a service is unreachable. Users should assign an Error Trigger workflow to each monitoring workflow to capture and report execution failures.
Sources: packages/@n8n/workflow-sdk/src/prompts/best-practices/guides/monitoring.ts:9-11, packages/@n8n/workflow-sdk/src/prompts/best-practices/guides/monitoring.ts:46-53
Heartbeat Monitoring
To monitor the monitoring system itself, n8n recommends using external heartbeat services like healthchecks.io. The workflow pings the external service to confirm it is still running; if the ping stops, the external service issues an alert.
Sources: packages/@n8n/workflow-sdk/src/prompts/best-practices/guides/monitoring.ts:54-58
Data Flow for Monitoring
The following diagram illustrates the standard flow for a service monitoring workflow:
The workflow checks service status at regular intervals and routes to alerts or logs based on the response.
Sources: packages/@n8n/workflow-sdk/src/prompts/best-practices/guides/monitoring.ts:13-16
Summary
The Telemetry and Observability framework provides developers and operators with the tools to track system usage, audit security, and ensure performance stability. By combining internal event registries, comprehensive performance benchmarking, and structured monitoring patterns, n8n maintains visibility across its monorepo architecture.