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
|**Active Connections**|`active_connections`|Count |Total number of connections to database Server, covering all states of connections, including active, idle, and others as seen in `pg_stat_activity` view. For a detailed view focusing solely on active connections, use "Sessions By State" metric. |Yes |
31
+
|**Active Connections**|`active_connections`|Count |Total number of connections to the database server, including all connection states such as active, idle, and others, as seen in `pg_stat_activity` view. This figure represents the overall sum of connections across all states, without distinguishing between specific states. For an in-depth analysis on a specific state, such as active connections, refer to the 'Sessions By State' metric. |Yes |
32
32
|**Backup Storage Used**|`backup_storage_used`|Bytes |Amount of backup storage used. This metric represents the sum of storage that's consumed by all the full backups, differential backups, and log backups that are retained based on the backup retention period that's set for the server. The frequency of the backups is service managed. For geo-redundant storage, backup storage usage is twice the usage for locally redundant storage.|Yes |
33
33
|**Failed Connections**|`connections_failed`|Count |Number of failed connections. |Yes |
34
34
|**Succeeded Connections**|`connections_succeeded`|Count |Number of succeeded connections. |Yes |
@@ -75,9 +75,9 @@ You can choose from the following categories of enhanced metrics:
|**Sessions By State**|`sessions_by_state`|Count|Overall state of the backend. |State|No|
79
-
|**Sessions By WaitEventType**|`sessions_by_wait_event_type`|Count|Sessions by the type of event for which the back end is waiting.|Wait Event Type|No|
80
-
|**Oldest Backend**|`oldest_backend_time_sec`|Seconds|Age in seconds of the oldest back end (irrespective of the state).|Doesn't apply|No|
78
+
|**Sessions By State**|`sessions_by_state`|Count|Sessions by state as shown in `pg_stat_activity` view. It categorizes client backends into various states, such as active or idle. |State|No|
79
+
|**Sessions By WaitEventType**|`sessions_by_wait_event_type`|Count|Sessions by the type of event for which the client backend is waiting.|Wait Event Type|No|
80
+
|**Oldest Backend**|`oldest_backend_time_sec`|Seconds|Age in seconds of the oldest backend (irrespective of the state).|Doesn't apply|No|
81
81
|**Oldest Query**|`longest_query_time_sec`|Seconds|Age in seconds of the longest query that's currently running. |Doesn't apply|No|
82
82
|**Oldest Transaction**|`longest_transaction_time_sec`|Seconds|Age in seconds of the longest transaction (including idle transactions).|Doesn't apply|No|
83
83
|**Oldest xmin**|`oldest_backend_xmin`|Count|The actual value of the oldest `xmin`. If `xmin` isn't increasing, it indicates that there are some long-running transactions that can potentially hold dead tuples from being removed. |Doesn't apply|No|
@@ -136,11 +136,11 @@ You can choose from the following categories of enhanced metrics:
136
136
- Enhanced metrics that use the DatabaseName dimension have a *50-database* limit.
137
137
- On the *Burstable* SKU, the limit is 10 databases for metrics that use the DatabaseName dimension.
138
138
- The DatabaseName dimension limit is applied on the database identifier (datid) column of the pg_stat_database system view, which reflects the order of creation for the database.
139
-
- The DatabaseName in the metrics dimension is *case insensitive*. That means that after querying pg_catalog.pg_stat_database, filtering out rows in which datname is either "template1" or "template0", ordering by datid, and limiting the returned rows to the first 50 (or 10 in the case of *Burstable* SKU), the metrics for database names in that result set, that are the same except for case (for example, *contoso_database* and *Contoso_database*) will be merged and might not show accurate data.
139
+
- The `DatabaseName` in the metrics dimension is *case insensitive*. That means that after querying `pg_stat_database` view, filtering out rows in which `datname` is either `template1` or `template0`, ordering by `datid`, and limiting the returned rows to the first 50 (or 10 in the case of *Burstable* SKU), the metrics for database names in that result set, that are the same except for case (for example, `contoso_database` and `Contoso_database`) will be merged and might not show accurate data.
140
140
141
141
### Autovacuum metrics
142
142
143
-
Autovacuum metrics can be used to monitor and tune autovacuum performance for Azure Database for PostgreSQL flexible server. Each metric is emitted at a *30-minute* interval and has up to *93 days* of retention. You can create alerts for specific metrics, and you can split and filter metrics data by using the DatabaseName dimension.
143
+
Autovacuum metrics can be used to monitor and tune autovacuum performance for Azure Database for PostgreSQL - Flexible Server. Each metric is emitted at a *30-minute* interval and has up to *93 days* of retention. You can create alerts for specific metrics, and you can split and filter metrics data by using the `DatabaseName` dimension.
144
144
145
145
#### How to enable autovacuum metrics
146
146
@@ -186,10 +186,10 @@ You can use PgBouncer metrics to monitor the performance of the PgBouncer proces
|**Active client connections**|`client_connections_active`|Count|Connections from clients that are associated with an Azure Database for PostgreSQL flexible server connection. |DatabaseName|No |
190
-
|**Waiting client connections**|`client_connections_waiting`|Count|Connections from clients that are waiting for an Azure Database for PostgreSQL flexible server connection to service them.|DatabaseName|No |
191
-
|**Active server connections**|`server_connections_active`|Count|Connections to Azure Database for PostgreSQL flexible server that are in use by a client connection. |DatabaseName|No |
192
-
|**Idle server connections**|`server_connections_idle`|Count|Connections to Azure Database for PostgreSQL flexible server that are idle and ready to service a new client connection. |DatabaseName|No |
189
+
|**Active client connections**|`client_connections_active`|Count|Connections from clients that are associated with an Azure Database for PostgreSQL - Flexible Server connection. |DatabaseName|No |
190
+
|**Waiting client connections**|`client_connections_waiting`|Count|Connections from clients that are waiting for an Azure Database for PostgreSQL - Flexible Server connection to service them.|DatabaseName|No |
191
+
|**Active server connections**|`server_connections_active`|Count|Connections to Azure Database for PostgreSQL - Flexible Server that are in use by a client connection. |DatabaseName|No |
192
+
|**Idle server connections**|`server_connections_idle`|Count|Connections to Azure Database for PostgreSQL - Flexible Server that are idle and ready to service a new client connection. |DatabaseName|No |
193
193
|**Total pooled connections**|`total_pooled_connections`|Count|Current number of pooled connections. |DatabaseName|No |
194
194
|**Number of connection pools**|`num_pools`|Count|Total number of connection pools. |DatabaseName|No |
195
195
@@ -205,7 +205,7 @@ Is-db-alive is a database server availability metric for Azure Database for Post
205
205
206
206
|Display Name |Metric ID |Unit |Description |Dimension |Default enabled|
0 commit comments