fix(webapp): oxfmt the metrics module and simplify the server-changes note

Run oxfmt on databaseMetrics.server.ts (code-quality check). Reword the
server-changes note to a single user-facing sentence with no infra names, per
the release-note guidance.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KHjfL7qXHia5DTnxi1RePS
This commit is contained in:
Eric Allam
2026-08-09 19:06:16 +01:00
parent 0a93dc087d
commit 2ec585b41b
2 changed files with 2 additions and 5 deletions
@@ -3,4 +3,4 @@ area: webapp
type: improvement
---
Database connection-pool and query metrics are now reported for every configured database connection rather than only the primary, and keep working regardless of which database driver a connection uses. These metrics are now emitted only through the OpenTelemetry exporter; the Prometheus `/metrics` endpoint no longer includes the `prisma_*` series, so if you scrape that endpoint for database metrics, enable the OpenTelemetry metric exporter instead.
Database connection metrics are now reported for every configured database connection instead of only the primary one, and stay accurate regardless of connection type.
@@ -52,10 +52,7 @@ export type NormalizedDatabaseMetrics = {
};
};
const sources = singleton(
"databaseMetricsSources",
() => new Map<string, DatabaseMetricsSource>()
);
const sources = singleton("databaseMetricsSources", () => new Map<string, DatabaseMetricsSource>());
export function registerDatabaseMetricsSource(source: DatabaseMetricsSource): void {
sources.set(source.clientType, source);