Skip to content

Database Metrics

This page documents Prometheus metrics related to user databases in the Yellowbrick system. These metrics reflect internal catalog states, transaction aging, and user data sizing across distributed storage.

Purpose

These metrics are primarily used to:

  • Monitor database size and catalog footprint
  • Detect potential transaction ID wraparound risks
  • Track compression and table count trends across databases

They are valuable for capacity planning, transaction maintenance (e.g. VACUUM), and debugging database-level anomalies or storage bloat.

Metrics

NameTypeFreqLabelsVersion IntroducedVersion DeprecatedDescription
yb_database_age_frozen_transaction_idgauge1hdatabase_oid7.3.0-Age of the oldest transaction ID that has not been frozen in the database
yb_database_age_minimum_multi_transaction_idgauge1hdatabase_oid7.3.0-Age of the oldest multi-transaction ID that has been replaced with a transaction ID in the database
yb_database_catalog_data_bytesgauge1hdatabase_oid7.3.0-Catalog and metadata size of the database
yb_database_table_countgauge1hdatabase_oid7.3.0-Number of user tables in each database
yb_database_user_data_compressed_bytesgauge1hdatabase_oid7.3.0-Compressed user data size for the database (worker nodes)
yb_temp_object_countgauge5mdatabase_oid7.3.2-Total number of temporary objects in each database
yb_temp_object_orphaned_countgauge5mdatabase_oid7.3.2-Total number of orphaned temporary objects in each database