Skip to content

[Backend] pg-pool.ts does not expose pool metrics (total/idle/waiting) to the admin metrics endpoint #1023

Description

@grantfox-oss

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

backend/src/lib/pg-pool.ts creates the raw pg.Pool used alongside Prisma, but its connection metrics are never surfaced anywhere, making it hard to diagnose connection exhaustion in production without shelling into the box.

Acceptance criteria

  • Expose pool.totalCount/idleCount/waitingCount via a small getter
  • Surface these values in the existing admin metrics response

Files to touch

  • backend/src/lib/pg-pool.ts
  • backend/src/routes/v1/admin.routes.ts

Out of scope

Does not add a new monitoring/alerting integration.

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programbackendBackend related tasksenhancementNew feature or requestinfraCI/CD and infrastructure

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions