Metrics latency

The PG AI Hybrid Manager collects and displays a wide range of observability data to give you comprehensive visibility into your database clusters.

The refresh intervals for these metrics vary depending on the metric and database type. This difference is due to the varying methods of data collection and integration.

Understanding data latency

When you view your database metrics in the Console, the data you see is the result of a two-step process, each with its own refresh interval. Understanding both steps will help you understand how up-to-date your metrics are.

Backend refresh: This is the first step, where the Hybrid Manager's internal services actively collect updated metrics and data from your database clusters. Whether your cluster is HM-managed or an external database, the backend systems are constantly gathering the latest information. This data is then stored in the Hybrid Manager's central data stores.

PG AI Console refresh: This is the second step, where the PG AI Console makes calls to your central data stores to retrieve the most recently collected data and display it to you.

The actual latency of the data you see in the Console is a combination of these two refresh intervals. The data on the screen will reflect information that is not older than the sum of these two intervals. In many cases, it will be much fresher, sometimes just seconds old.

Refresh intervals

Backend refresh: The Hybrid Manager's internal services update the data stores as follows. The interval varies depending on the database cluster type and the metrics context.

These intervals are configurable for self-managed and CSP-managed clusters. To customize the frequency of data collection for self-managed clusters, define the intervals in the PG AI Agent configuration YAML. In the case of CSP-managed clusters, define the intervals for the supported metrics through the beacon-csp-credentials configuration.

PG AI Console refresh: The PG AI Console updates the data for all cluster types with the following frequency: