Azure Database for PostgreSQL (Single Server, Hyperscale, Flexible Server) monitoring

  • How-to guide
  • 6-min read
  • Published Jun 25, 2020

On the Azure Database for PostgreSQL (Single Server, Hyperscale, Flexible Server) overview pages you get insights into various aspects of database performance, including CPU and memory usage, active connections, storage space, and much more.

Prerequisites

  • Dynatrace version 1.196+
  • Environment ActiveGate version 1.195+

Enable monitoring

To learn how to enable service monitoring, see Enable service monitoring.

Optionally, for OneAgent integration, see how database activity is monitored.

View service metrics

You can view the service metrics in your Dynatrace environment either on the custom device overview page or on your Dashboards page.

View metrics on the custom device overview page

To access the custom device overview page

  1. Go to Technologies & Processes Classic.
  2. Filter by service name and select the relevant custom device group.
  3. Once you select the custom device group, you're on the custom device group overview page.
  4. The custom device group overview page lists all instances (custom devices) belonging to the group. Select an instance to view the custom device overview page.

View metrics on your dashboard

Once you add a service to monitoring, a preset dashboard for the respective service containing all recommended metrics is automatically created on your Dashboards page. You can look for specific dashboards by filtering by Preset and then by Name.

For existing monitored services, you might need to resave your credentials for the preset dashboard to appear on the Dashboards page. To resave your credentials, go to Settings > Cloud and virtualization > Azure, select the desired Azure instance, then select Save.

You can't make changes on a preset dashboard directly, but you can clone and edit it. To clone a dashboard, open the browse menu () and select Clone.
To remove a dashboard from the dashboards list, you can hide it. To hide a dashboard, open the browse menu () and select Hide.

Hiding a dashboard doesn't affect other users.

Clone hide azure

Postgres dash

Hyper

Set up a management zone

To import a dashboard for Azure Database for PostgreSQL, you need to set up a management zone to limit the entities displayed on the dashboard to those relevant to this service.

When you create a management zone for this dashboard:

  1. Create a rule that identifies services based on a common property:
    • Service topology: Opaque service
    • Service type: Database
  2. Add a condition for the database name to contain the postgres string (case sensitive.)

Azure management zone

You can see whether a dashboard requires a management zone in the rules setup.

After you create the management zone, assign it to your dashboard (from the dashboard, select Edit > Settings > Default management zone). For more information, see Dashboard timeframe and management zone.

Available metrics

Azure Database for PostgreSQL (Single Server)

NameDescriptionUnitRecommended
active_connectionsThe number of active connections to the serverCountApplicable
backup_storage_usedThe amount of backup storage used. This metric represents the sum of storage consumed by all the full database backups, differential backups, and log backups retained based on the backup retention period set for the server.Bytes
cpu_percentThe percentage of CPU in usePercentApplicable
connections_failedThe number of established connections that failedCountApplicable
io_consumption_percentThe percentage of IO in usePercentApplicable
pg_replica_log_delay_in_bytesLag in bytes of the most lagging replicaBytes
memory_percentThe percentage of memory in usePercentApplicable
network_bytes_ingressNetwork in across active connectionsBytesApplicable
network_bytes_egressNetwork out across active connectionsBytesApplicable
pg_replica_log_delay_in_secondsThe time since the last replayed transaction. This metric is available for replica servers only.SecondsApplicable
serverlog_storage_limitThe maximum server log storage for this serverBytes
serverlog_storage_percentThe percentage of server log storage used out of the server's maximum server log storagePercentApplicable
serverlog_storage_usageThe amount of server log storage in useBytes
storage_limitThe maximum storage for this serverBytes
storage_percentThe percentage of storage used out of the server's maximumPercentApplicable
storage_usedThe amount of storage in use. The storage used by the service may include the database files, transaction logs, and the server logs.Bytes

Azure Database for PostgreSQL Hyperscale

NameDescriptionUnitRecommended
active_connectionsThe number of active connections to the serverCountApplicable
cpu_percentThe percentage of CPU in usePercentApplicable
iopsThe number of requests that your application is sending to the storage disks in one secondCountApplicable
memory_percentThe percentage of memory in usePercentApplicable
network_bytes_egressNetwork out across active connectionsByteApplicable
network_bytes_ingressNetwork in across active connectionsByteApplicable
storage_percentThe percentage of storage used out of the server's maximumPercentApplicable
storage_usedThe amount of storage in use. The storage used by the service may include the database files, transaction logs, and the server logs.Byte

Azure Database for PostgreSQL - Flexible Server

NameDescriptionUnitRecommended
active_connectionsNumber of connections to your server.CountApplicable
backup_storage_usedAmount of backup storage used. This metric represents the sum of storage consumed by all the full database backups, differential backups, and log backups retained based on the backup retention period set for the server. The frequency of the backups is service managed. For geo-redundant storage, backup storage usage is twice that of the locally redundant storage.Byte
connections_failedFailed connections.CountApplicable
connections_succeededSucceeded connections.Count
cpu_credits_consumedNumber of credits used by the flexible server. Applicable to Burstable tier.Count
cpu_credits_remainingNumber of credits available to burst. Applicable to Burstable tier.Count
cpu_percentPercentage of CPU in use.PercentApplicable
disk_queue_depthNumber of outstanding I/O operations to the data disk.Count
iopsNumber of I/O operations to disk per second.CountApplicable
maximum_used_transactionIDsMaximum transaction ID in use.Count
memory_percentPercentage of memory in use.PercentApplicable
network_bytes_ingressAmount of incoming network traffic.ByteApplicable
network_bytes_egressAmount of outgoing network traffic.ByteApplicable
read_iopsNumber of data disk I/O read operations per second.Count
read_throughputBytes read per second from disk.CountApplicable
storage_freeAmount of storage space available.Byte
storage_percentPercent of storage space used. The storage used by the service may include the database files, transaction logs, and the server logs.PercentApplicable
storage_usedThe storage used by the service may include the database files, transaction logs, and the server logs.Byte
txlogs_storage_usedAmount of storage space used by the transaction logs.Byte
write_iopsNumber of data disk I/O write operations per second.Count
write_throughputBytes written per second to disk.CountApplicable
Related tags
Infrastructure Observability