feat(core): Add Prometheus metrics for n8n Insights data

[craftaholic]

Summary

This PR adds Prometheus metrics integration for n8n Insights data, allowing workflow analytics to be exposed to external monitoring systems like Datadog and Grafana.

Key Features:

• 5 new Prometheus metrics for insights data (avg runtime, failures, failure rate, time saved, total
  executions)
• Event-driven architecture that emits metrics when insights are calculated
• Configurable via N8N_METRICS_INCLUDE_INSIGHTS_METRICS environment variable
• Comprehensive documentation with integration examples

How to Test:

1. Set environment variables:

• N8N_METRICS=true
• N8N_METRICS_INCLUDE_INSIGHTS_METRICS=true

2. Navigate to insights dashboard to trigger calculations
3. Check /metrics endpoint for new insights metrics

Related Linear tickets, Github issues, and Community forum posts

Review / Merge checklist

• PR title and summary are descriptive. (conventions)
• Docs updated or follow-up ticket created.
• Tests included.
• PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

[CLAassistant]

All committers have signed the CLA.

[cubic-dev-ai]

1 issue found across 7 files

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name="packages/cli/src/metrics/prometheus-metrics.service.ts">

<violation number="1" location="packages/cli/src/metrics/prometheus-metrics.service.ts:345">
The insights metrics listener subscribes to MessageEventBus, but insights events are emitted via EventService. As a result, these gauges won’t update. Subscribe to the same event system used by the emitter (or relay the EventService event to the bus) before processing insights-metrics-calculated.</violation>
</file>

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Ask questions if you need clarification on any suggestion

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}

[cubic-dev-ai]

The insights metrics listener subscribes to MessageEventBus, but insights events are emitted via EventService. As a result, these gauges won’t update. Subscribe to the same event system used by the emitter (or relay the EventService event to the bus) before processing insights-metrics-calculated.

Prompt for AI agents

Address the following comment on packages/cli/src/metrics/prometheus-metrics.service.ts at line 345:

<comment>The insights metrics listener subscribes to MessageEventBus, but insights events are emitted via EventService. As a result, these gauges won’t update. Subscribe to the same event system used by the emitter (or relay the EventService event to the bus) before processing insights-metrics-calculated.</comment>

<file context>
@@ -297,6 +299,75 @@ export class PrometheusMetricsService {
+		});
+		
+		// Set up event listener for insights metrics events
+		this.eventBus.on(&#39;metrics.eventBus.event&#39;, (event) =&gt; {
+			if (event.eventName === &#39;insights-metrics-calculated&#39;) {
+				const { metricType, period, value, projectId } = event.payload;
</file context>

[n8n-assistant]

Hey @craftaholic,

Thank you for your contribution. We appreciate the time and effort you’ve taken to submit this pull request.

Before we can proceed, please ensure the following:
• Tests are included for any new functionality, logic changes or bug fixes.
• The PR aligns with our contribution guidelines.

Regarding new nodes:
We no longer accept new nodes directly into the core codebase. Instead, we encourage contributors to follow our Community Node Submission Guide to publish nodes independently.

If your node integrates with an AI service that you own or represent, please email [email protected] and we will be happy to discuss the best approach.

About review timelines:
This PR has been added to our internal tracker as "GHC-4983". While we plan to review it, we are currently unable to provide an exact timeframe. Our goal is to begin reviews within a month, but this may change depending on team priorities. We will reach out when the review begins.

Thank you again for contributing to n8n.