Skip to content

fix(metrics): maxwait description #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
meskill merged 1 commit into from
Mar 19, 2026
Merged

fix(metrics): maxwait description #60

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/administration/pools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,8 @@ The following information is returned for each connection pool (user/database pa
| `sv_active` | Number of checked out (used) server connections in the pool. | `12` |
| `sv_idle_xact` | Number of idle-in-transaction server connections in the pool. | `0` |
| `sv_total` | Total number of server connections in the pool. | `20` |
| `maxwait` | Maximum wait time for connections. | `30` |
| `maxwait_us` | Maximum wait time for connections in microseconds. | `30000000` |
| `maxwait` | How long the first (oldest) client in the queue has waited, in seconds. | `30` |
| `maxwait_us` | Microsecond part of the `maxwait` value. | `30000000` |
| `pool_mode` | Connection pooling mode. | `transaction` |
| `paused` | The pool is paused and won't issue connections until resumed. | `f` |
| `banned` | The pool is blocked from serving more clients. | `f` |
Expand Down
2 changes: 1 addition & 1 deletion docs/enterprise_edition/metrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,5 +29,5 @@ The default value is **1 second**, which should be sufficient to debug most prod
Once the metrics reach the control plane, they are pushed down to the web dashboard via a real-time connection. Per-minute aggregates are computed in the background and stored in a separate PostgreSQL database, which provides a historical view into overall database performance.

<center>
<img src="/images/ee/metrics.png" width="100%" alt="How PgDog works" class="screenshot" />
<img src="/images/ee/metrics.png" width="100%" alt="PgDog Real-time Metrics" class="screenshot" />
</center>
2 changes: 1 addition & 1 deletion docs/features/metrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ The following metrics are exported via the OpenMetrics endpoint:
| `sv_active` | Servers currently serving client requests. | `gauge` |
| `sv_idle` | Servers available for clients to use. | `gauge` |
| `sv_idle_xact` | Servers currently idle in transaction. | `gauge` |
| `maxwait` | How long clients have been waiting for a connection (in seconds). | `gauge` |
| `maxwait` | How long the first (oldest) client in the queue has waited (in seconds). | `gauge` |
| `errors` | Errors that connections in the pool have experienced. | `counter` |
| `out_of_sync` | Connections that have been returned to the pool in a broken state. | `counter` |
| `total_xact_count` | Total number of executed transactions. | `counter` |
Expand Down
Loading