ruicesar/InfiniteAPI
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: use different metric name to avoid conflict with collectDefaultMetrics

Browse Source
This commit is contained in:
Claude
2026-01-22 04:13:42 +00:00
parent 931ef71250
commit b5b43b5fd6
1 changed files with 6 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/Utils/prometheus-metrics.ts
+6 -9
View File
@@ -1076,15 +1076,12 @@ export class SystemMetricsCollector {
new Gauge('system_load_average', 'System load average', ['period'])
)
// Event loop lag - check if already exists (may be created by collectDefaultMetrics)
const existingEventLoopLag = getExistingMetric<Histogram>('nodejs_eventloop_lag_seconds')
if (existingEventLoopLag) {
this.eventLoopLag = existingEventLoopLag
} else {
this.eventLoopLag = registry.register(
new Histogram('nodejs_eventloop_lag_seconds', 'Event loop lag in seconds', [], DEFAULT_LATENCY_BUCKETS)
)
}
// Event loop lag - use different name to avoid conflict with collectDefaultMetrics
// prom-client's collectDefaultMetrics creates nodejs_eventloop_lag_seconds
// We use system_eventloop_lag_seconds to avoid duplicate registration
this.eventLoopLag = registry.register(
new Histogram('system_eventloop_lag_seconds', 'Event loop lag in seconds', [], DEFAULT_LATENCY_BUCKETS)
)
// Initialize CPU baseline
this.lastCpuUsage = process.cpuUsage()