You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/postgresql/flexible-server/concepts-monitoring.md
+29-3Lines changed: 29 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,7 +120,7 @@ Introducing Enhanced Metrics for Azure Database for PostgreSQL Flexible Server t
120
120
121
121
- There is **50 database** limit on metrics with `database name` dimension.
122
122
* On **Burstable** SKU - this limit is 10 `database name` dimension
123
-
-`database name` dimension limit is applied on OiD column (in other words Order-of-Creation of the database)
123
+
-`database name` dimension limit is applied on OiD column (in other words _Order-of-Creation_ of the database)
124
124
- The `database name` in metrics dimension is **case insensitive**. Therefore the metrics for same database names in varying case (_ex. foo, FoO, FOO_) will be merged, and may not show accurate data.
125
125
126
126
## Autovacuum metrics
@@ -132,7 +132,7 @@ Autovaccum metrics can be used to monitor and tune autovaccum performance for Az
132
132
* To enable these metrics, please turn ON the server parameter `metrics.autovacuum_diagnostics`.
133
133
* This parameter is dynamic, hence will not require instance restart.
134
134
135
-
#### Autovacuum metrics
135
+
#### List of Autovacuum metrics
136
136
137
137
|Display Name |Metric ID |Unit |Description |Dimension |Default enabled|
@@ -153,7 +153,33 @@ Autovaccum metrics can be used to monitor and tune autovaccum performance for Az
153
153
154
154
- There is **30 database** limit on metrics with `database name` dimension.
155
155
* On **Burstable** SKU - this limit is 10 `database name` dimension
156
-
-`database name` dimension limit is applied on OiD column (in other words Order-of-Creation of the database)
156
+
-`database name` dimension limit is applied on OiD column (in other words _Order-of-Creation_ of the database)
157
+
158
+
## PgBouncer metrics
159
+
160
+
PgBouncer metrics can be used for monitoring the performance of PgBouncer process, including details for active connections, Idle connections, Total pooled connections, number of connection pools etc. Each metric is emitted at a **30 minute** frequency and has up to **93 days** of history. Customers can configure alerts on the metrics and can also access the new metrics dimensions, to split and filter the metrics data on database name.
161
+
162
+
#### Enabling PgBouncer metrics
163
+
* PgBouncer metrics are disabled by default.
164
+
* For Pgbouncer metrics to work, both the server parameters `pgbouncer.enabled` and `metrics.pgbouncer_diagnostics` have to be enabled.
165
+
* These parameters are dynamic, and will not require instance restart.
166
+
167
+
#### List of PgBouncer metrics
168
+
169
+
|Display Name |Metrics ID |Unit |Description |Dimension |Default enabled|
|**Active client connections** (Preview) |client_connections_active |Count|Connections from clients which are associated with a PostgreSQL connection |DatabaseName|No |
172
+
|**Waiting client connections** (Preview)|client_connections_waiting|Count|Connections from clients that are waiting for a PostgreSQL connection to service them|DatabaseName|No |
173
+
|**Active server connections** (Preview) |server_connections_active |Count|Connections to PostgreSQL that are in use by a client connection |DatabaseName|No |
174
+
|**Idle server connections** (Preview) |server_connections_idle |Count|Connections to PostgreSQL that are idle, ready to service a new client connection |DatabaseName|No |
175
+
|**Total pooled connections** (Preview) |total_pooled_connections |Count|Current number of pooled connections |DatabaseName|No |
176
+
|**Number of connection pools** (Preview)|num_pools |Count|Total number of connection pools |DatabaseName|No |
177
+
178
+
#### Considerations when using the PgBouncer metrics
179
+
180
+
- There is **30 database** limit on metrics with `database name` dimension.
181
+
* On **Burstable** SKU - this limit is 10 `database name` dimension.
182
+
-`database name` dimension limit is applied on OiD column (in other words _Order-of-Creation_ of the database)
157
183
158
184
## Applying filters and splitting on metrics with dimension
0 commit comments