Skip to main content

Cluster-agent

This page describes metrics gathered by coroot-cluster-agent.

Coroot-cluster-agent is a dedicated tool for collecting cluster-wide telemetry data:

  • It gathers database metrics by discovering databases through Coroot's Service Map and Kubernetes control-plane. Using the credentials provided by Coroot or via Kubernetes annotations, the agent connects to the identified databases such as Postgres, MySQL, Redis, Memcached, and MongoDB, collects database-specific metrics, and sends them to Coroot using the Prometheus Remote Write protocol.
  • When --track-database-changes is enabled, the agent tracks schema and configuration changes in databases. Change events are sent to Coroot as OpenTelemetry log records under the DatabaseChanges service name.
  • The agent can be integrated with AWS to discover RDS and ElastiCache clusters and collect their telemetry data.
  • The agent discovers and scrapes custom metrics from annotated pods.
  • The agent monitors GitOps tooling by reading FluxCD and ArgoCD custom resources through its embedded kube-state-metrics and exposing their state as metrics.
  • The agent monitors Postgres backups of clusters managed by CloudNativePG and the Percona Operator for PostgreSQL, reading their custom resources through the embedded kube-state-metrics.

Postgres​

pg_up​

  • Description: Whether the Postgres server is reachable or not
  • Type: Gauge
  • Source: The agent checks that a connection to the server is still alive on each scrape

pg_probe_seconds​

  • Description: How long it took to execute an empty SQL query (;) on the server. This metric shows the round-trip time between the agent and the server
  • Type: Gauge
  • Source: The time spent executing db.Ping()

pg_scrape_error​

  • Description: Whether a scrape error occurred
  • Type: Gauge
  • Labels: error, warning

pg_info​

pg_setting​

  • Description: Value of the pg_setting variable
  • Type: Gauge
  • Source: pg_settings. The agent only collects variables of the following types: integer, real and bool
  • Labels: name, unit

pg_connections​

  • Description: The number of the database connections
  • Type: Gauge
  • Source: pg_stat_activity
  • Labels:
    • db
    • user
    • state: current state of the connection, < active | idle | idle in transaction >
    • wait_event_type: type of event that the connection is waiting for.
    • query - If the state of a connection is active, this is the currently executing query. For idle in transaction connections, this is the last executed query. This label holds a normalized and obfuscated query.

pg_autovacuum_workers​

  • Description: Number of running autovacuum worker processes
  • Type: Gauge
  • Source: pg_stat_activity (backend_type = 'autovacuum worker')

pg_latency_seconds​

pg_db_queries_per_second​

  • Description: Number of queries executed in the database
  • Type: Gauge
  • Source: Aggregation of pg_stat_activity.state = 'Active' and pg_stat_statements.calls
  • Labels: db

pg_lock_awaiting_queries​

  • Description: Number of queries awaiting a lock
  • Type: Gauge
  • Source: Number of connections with pg_stat_activity.wait_event_type = 'Lock'. The blocking_query label is calculated using the pg_blocking_pids function
  • Labels: db, user, blocking_query (the query holding the lock)

Query Metrics​

The pg_stat_statements view shows statistics only for queries that have been completed. So, to provide comprehensive statistics, the agent extends this with data about the currently active queries from the pg_stat_activity view.

Collecting stats about each query would produce metrics with very high cardinality. However, the primary purpose of such metrics is to show the most resource-consuming queries. So, the agent collects these metrics only for TOP-20 queries by total execution time.

Each metric described below has query, db and user labels. Query is a normalized and obfuscated query from pg_stat_statements.query, and pg_stat_activity.query.

For example, the following queries:

SELECT * FROM tbl WHERE id='1';
SELECT * FROM tbl WHERE id='2';

will be grouped to

SELECT * FROM tbl WHERE id=?;

pg_top_query_calls_per_second​

  • Description: Number of times the query has been executed
  • Type: Gauge
  • Source: pg_stat_statements.calls and pg_stat_activity.state = 'Active'
  • Labels: db, user, query

pg_top_query_time_per_second​

  • Description: Time spent executing the query
  • Type: Gauge
  • Source: clock_timestamp()-pg_stat_activity.query_start and pg_stat_statements.total_time
  • Labels: db, user, query

pg_top_query_io_time_per_second​

  • Description: Time the query spent awaiting I/O
  • Type: Gauge
  • Source: pg_stat_activity.wait_event_type = 'IO', pg_stat_statements.blk_read_time and pg_stat_statements.blk_write_time
  • Labels: db, user, query

Replication metrics​

pg_wal_receiver_status​

  • Description: WAL receiver status: 1 if the receiver is connected, otherwise 0
  • Type: Gauge
  • Source: pg_stat_wal_receiver and pg_settings[primary_conninfo]
  • Labels: sender_host, sender_port

pg_wal_replay_paused​

  • Description: Whether WAL replay paused or not
  • Type: Gauge
  • Source: pg_is_wal_replay_paused() or pg_is_xlog_replay_paused()

pg_wal_current_lsn​

  • Description: Current WAL sequence number
  • Type: Counter
  • Source: pg_current_wal_lsn() or pg_current_xlog_location()

pg_wal_receive_lsn​

  • Description: WAL sequence number that has been received and synced to disk by streaming replication.
  • Type: Counter
  • Source: pg_last_wal_receive_lsn() or pg_last_xlog_receive_location()

pg_wal_reply_lsn​

  • Description: WAL sequence number that has been replayed during recovery
  • Type: Counter
  • Source: pg_last_wal_replay_lsn() or pg_last_xlog_replay_location()

WAL size and archiving​

pg_wal_size_bytes​

  • Description: Size of the WAL directory
  • Type: Gauge
  • Source: pg_ls_waldir()

pg_replication_slot_retained_wal_bytes​

  • Description: Amount of WAL retained for the replication slot
  • Type: Gauge
  • Source: pg_replication_slots (restart_lsn); wal_status is reported on Postgres >= 13
  • Labels: slot, active, wal_status

pg_wal_archived_segments_total​

  • Description: Number of WAL files successfully archived
  • Type: Counter
  • Source: pg_stat_archiver

pg_wal_archive_failures_total​

  • Description: Number of failed attempts to archive WAL files
  • Type: Counter
  • Source: pg_stat_archiver

pg_wal_archiving_status​

  • Description: 1 if the last WAL archive attempt succeeded, 0 if it failed
  • Type: Gauge
  • Source: pg_stat_archiver

Checkpoint metrics​

The agent tracks checkpoint activity from pg_stat_checkpointer (Postgres >= 17) or pg_stat_bgwriter (older versions). The counters are rebased and accumulated over the agent's lifetime.

pg_checkpoints_scheduled_total​

  • Description: Number of scheduled checkpoints, including skipped ones
  • Type: Counter
  • Source: pg_stat_checkpointer (Postgres >= 17) or pg_stat_bgwriter
  • Labels: type (timed, requested)

pg_checkpoints_total​

  • Description: Number of checkpoints that have been completed
  • Type: Counter
  • Source: pg_stat_checkpointer (Postgres >= 17) or pg_stat_bgwriter

pg_restartpoints_total​

  • Description: Number of restartpoints that have been completed on a standby
  • Type: Counter
  • Source: pg_stat_checkpointer.restartpoints_done (Postgres >= 17)

pg_buffers_written_total​

  • Description: Total number of dirty buffers flushed to disk
  • Type: Counter
  • Source: pg_stat_checkpointer (Postgres >= 17) or pg_stat_bgwriter
  • Labels: source (checkpointer)

pg_time_since_last_checkpoint_seconds​

  • Description: Seconds since the last checkpoint observed by the agent
  • Type: Gauge
  • Source: Measured by the agent from the checkpoint completion counter

pg_wal_since_last_checkpoint_bytes​

  • Description: Amount of WAL written since the last completed checkpoint (to be replayed in the case of a crash)
  • Type: Gauge
  • Source: pg_control_checkpoint() (redo_lsn)

Transaction ID age​

pg_xid_age​

  • Description: Transactions since the oldest unfrozen transaction ID (age of datfrozenxid)
  • Type: Gauge
  • Source: pg_database
  • Labels: db

pg_multixact_age​

  • Description: Multixacts since the oldest unfrozen multixact ID (age of datminmxid)
  • Type: Gauge
  • Source: pg_database
  • Labels: db

pg_oldest_xmin_age​

  • Description: Age, in transactions, of the oldest transaction ID held back from freezing, by holder
  • Type: Gauge
  • Source: pg_stat_activity, pg_replication_slots, pg_prepared_xacts (Postgres >= 10)
  • Labels: holder (running_transaction, standby_feedback, replication_slot, prepared_transaction)

Change tracking​

When --track-database-changes is enabled, the agent detects and emits change events for:

  • Schema changes — The agent periodically snapshots the DDL of every table (columns, constraints, indexes) across all databases. When a table's DDL changes between consecutive snapshots, a change event is emitted with a unified diff. Only schema modifications are tracked (e.g., ALTER TABLE, index creation/removal). The snapshot is collected by connecting to each database and querying pg_catalog and information_schema.
  • Settings changes — The agent snapshots all pg_settings values each cycle. When a setting changes (e.g., after a configuration reload or restart), a change event is emitted with the diff. Session-level and client-level overrides are excluded.

Each change event includes db.system, db.target, db.name, db_change.object, and db_change.type attributes.

Size and bloat metrics​

The agent collects database and table size metrics. For table sizes, only the top 20 largest tables across all databases are reported.

pg_database_size_bytes​

  • Description: Total size of the database in bytes
  • Type: Gauge
  • Source: pg_database_size()
  • Labels: db

pg_table_size_bytes​

  • Description: Total size of the table in bytes including indexes and TOAST
  • Type: Gauge
  • Source: pg_total_relation_size()
  • Labels: db, schema, table

pg_table_size_growth_bytes_per_second​

  • Description: Table size growth rate in bytes per second. Only the top 20 fastest growing tables across all databases are reported. Requires at least two collection cycles to compute.
  • Type: Gauge
  • Source: Computed from consecutive pg_total_relation_size() measurements
  • Labels: db, schema, table

When --track-database-bloat is enabled, the agent also estimates wasted space (bloat) for tables and indexes from planner statistics (pg_class.reltuples/relpages and pg_stats column widths), without scanning table data. TOAST relations are excluded, and only the top tables and indexes by estimated bloat are reported per database. Estimates are approximate and depend on up-to-date ANALYZE/autovacuum statistics.

pg_db_table_bloat_bytes​

  • Description: Estimated wasted space across all tables of the database
  • Type: Gauge
  • Source: Estimated from pg_class and pg_stats
  • Labels: db

pg_db_index_bloat_bytes​

  • Description: Estimated wasted space across all indexes of the database
  • Type: Gauge
  • Source: Estimated from pg_class and pg_stats
  • Labels: db

pg_table_bloat_bytes​

  • Description: Estimated wasted space in the table heap
  • Type: Gauge
  • Source: Estimated from pg_class and pg_stats
  • Labels: db, schema, table

pg_index_bloat_bytes​

  • Description: Estimated wasted space in the index
  • Type: Gauge
  • Source: Estimated from pg_class and pg_stats
  • Labels: db, schema, table, index

When --track-database-sizes is enabled, the agent also reports dead-row statistics — a leading indicator of autovacuum falling behind, distinct from bloat. The dead/live counts let Coroot compute autovacuum pressure (how many times past its own autovacuum trigger a table sits), and dead bytes provides materiality. All three are emitted from one query with one top-N ranking (by dead bytes), so every reported table carries the complete set.

pg_table_dead_tuple_bytes​

  • Description: Estimated size of dead tuples not yet reclaimed by vacuum (heap size × dead fraction)
  • Type: Gauge
  • Source: pg_stat_user_tables (n_dead_tup, n_live_tup) and pg_relation_size()
  • Labels: db, schema, table

pg_table_dead_tuples​

  • Description: Number of dead tuples not yet reclaimed by vacuum
  • Type: Gauge
  • Source: pg_stat_user_tables (n_dead_tup)
  • Labels: db, schema, table

pg_table_live_tuples​

  • Description: Estimated number of live tuples
  • Type: Gauge
  • Source: pg_stat_user_tables (n_live_tup)
  • Labels: db, schema, table

pg_table_seconds_since_last_autovacuum​

  • Description: Seconds since the last autovacuum of the table. Not reported for tables that have never been autovacuumed.
  • Type: Gauge
  • Source: pg_stat_user_tables (now() - last_autovacuum)
  • Labels: db, schema, table

pg_table_setting​

  • Description: Info metric (value always 1) carrying a table's per-table autovacuum and autoanalyze reloption overrides as labels. Reported only for tables that override at least one setting; an unset override is an empty label. Coroot uses the trigger overrides to compute pressure against the table's own vacuum and analyze triggers, and the cost overrides to pinpoint per-table throttling.
  • Type: Gauge
  • Source: pg_class.reloptions
  • Labels: db, schema, table, and the override values: autovacuum_disabled (1 when autovacuum_enabled=false, which disables autoanalyze too), autovacuum_vacuum_scale_factor, autovacuum_vacuum_threshold, autovacuum_vacuum_cost_delay, autovacuum_vacuum_cost_limit, autovacuum_analyze_scale_factor, autovacuum_analyze_threshold

pg_table_vacuum_in_progress​

  • Description: 1 if a vacuum is currently running on the table. Reported only while a vacuum is in progress. Lets Coroot tell a table that has a worker on it (possibly crawling) from one waiting for a free worker.
  • Type: Gauge
  • Source: pg_stat_progress_vacuum (Postgres >= 9.6)
  • Labels: db, schema, table

pg_table_vacuum_throttled​

  • Description: 1 if the running vacuum is sleeping on the cost-based delay (VacuumDelay wait event) at scrape time, 0 otherwise. Reported only while a vacuum is in progress; a high average means the vacuum is being throttled by autovacuum_vacuum_cost_delay/autovacuum_vacuum_cost_limit.
  • Type: Gauge
  • Source: pg_stat_progress_vacuum joined with pg_stat_activity (wait_event = 'VacuumDelay')
  • Labels: db, schema, table

pg_table_mods_since_analyze​

  • Description: Rows modified (inserted, updated, or deleted) since the table's planner statistics were last analyzed. Unlike dead tuples this includes inserts, so it is collected as its own top-N (ranked by analyze pressure) rather than reusing the dead-tuple set. Coroot divides it by the autoanalyze trigger to compute how stale the statistics are.
  • Type: Gauge
  • Source: pg_stat_user_tables (n_mod_since_analyze)
  • Labels: db, schema, table

pg_table_reltuples​

  • Description: The planner's estimate of the number of live rows in the table. Used as the denominator of analyze/vacuum pressure. Unlike n_live_tup it is persisted in pg_class, so it survives a replica promotion (which resets the cumulative pg_stat_* counters) and keeps pressure from spiking to a false value on a freshly promoted primary.
  • Type: Gauge
  • Source: pg_class.reltuples
  • Labels: db, schema, table

pg_table_seconds_since_last_analyze​

  • Description: Seconds since the table's planner statistics were last refreshed by ANALYZE or autoanalyze. Not reported for tables that have never been analyzed.
  • Type: Gauge
  • Source: pg_stat_user_tables (now() - greatest(last_analyze, last_autoanalyze))
  • Labels: db, schema, table

Postgres backups​

Backup state is collected through the agent's embedded kube-state-metrics from the custom resources of CloudNativePG (cnpg) and the Percona Operator for PostgreSQL (pgBackRest, percona). Every metric carries an operator label identifying the source and, via the common namespace/name labels, correlates to the corresponding DatabaseCluster application in Coroot, so a single operator-agnostic set of metrics powers the backup inspection.

pg_backup_target_info​

  • Description: A configured backup destination. cnpg reports a single object-storage target, and pgBackRest reports one series per repository. Coroot assembles the destination from the explicit path or the object-storage sub-fields.
  • Type: Info
  • Source: Cluster.spec.backup (cnpg), PerconaPGCluster.spec.backups.pgbackrest.repos (Percona)
  • Labels: operator, method, path, endpoint, s3_bucket, s3_endpoint, gcs_bucket, azure_container, schedule, retention_policy

pg_cluster_status​

  • Description: A cluster status condition (e.g. ReadyForBackup, LastBackupSucceeded, ContinuousArchiving, PGBackRestRepoHostReady). Value is 1 for the currently-active series. The reason feeds Coroot's "why backups are failing" hint.
  • Type: Info
  • Source: .status.conditions
  • Labels: operator, type, status, reason

pg_backup_last_successful_timestamp_seconds​

  • Description: Time of the last successful backup, per method. Reported by cnpg. For Percona it is derived from the individual backup runs.
  • Type: Gauge
  • Source: Cluster.status.lastSuccessfulBackupByMethod
  • Labels: operator, method

pg_backup_first_recoverability_point_timestamp_seconds​

  • Description: The oldest point in time the cluster can be restored to (start of the recovery window), per method.
  • Type: Gauge
  • Source: Cluster.status.firstRecoverabilityPointByMethod
  • Labels: operator, method

pg_backup_last_failed_timestamp_seconds​

  • Description: Time of the last failed backup.
  • Type: Gauge
  • Source: Cluster.status.lastFailedBackup
  • Labels: operator

pg_backup_schedule_info​

  • Description: The backup schedule (cron).
  • Type: Info
  • Source: ScheduledBackup.spec.schedule (cnpg)
  • Labels: operator, cluster, schedule

pg_backup_next_scheduled_timestamp_seconds​

  • Description: When the next scheduled backup is due. Coroot also derives an expected next run from the schedule and the last backup, so an overdue schedule is detected even when the operator stops advancing this value.
  • Type: Gauge
  • Source: ScheduledBackup.status.nextScheduleTime (cnpg)
  • Labels: operator, cluster

pg_backup_info​

  • Description: An individual backup run (one series per backup object), used to list recent backups. Carries immutable identity only. The run's phase is in pg_backup_status.
  • Type: Info
  • Source: Backup (cnpg), PerconaPGBackup (Percona)
  • Labels: operator, cluster, method, kind, path

pg_backup_status​

  • Description: The current phase of a backup run (e.g. Running, Succeeded, Failed, completed). Value is 1 for the currently-active series (a run's phase changes over its lifecycle, so only the live series is used).
  • Type: Info
  • Source: Backup.status.phase (cnpg), PerconaPGBackup.status.state (Percona)
  • Labels: operator, status

pg_backup_completed_timestamp_seconds​

  • Description: When a backup run completed.
  • Type: Gauge
  • Source: Backup.status.stoppedAt (cnpg), PerconaPGBackup.status.completed (Percona)
  • Labels: operator, cluster

MySQL​

mysql_up​

  • Description: Whether the MySQL server is reachable or not
  • Type: Gauge

mysql_scrape_error​

  • Description: Whether a scrape error occurred
  • Type: Gauge
  • Labels: error, warning

mysql_info​

  • Description: The server info
  • Type: Gauge
  • Labels: server_version, server_id, server_uuid

mysql_top_query_calls_per_second​

  • Description: Number of times the query has been executed
  • Type: Gauge
  • Source: performance_schema.events_statements_summary_by_digest
  • Labels: schema, query

mysql_top_query_time_per_second​

  • Description: Time spent executing the query
  • Type: Gauge
  • Source: performance_schema.events_statements_summary_by_digest
  • Labels: schema, query

mysql_top_query_lock_time_per_second​

  • Description: Time the query spent waiting for locks
  • Type: Gauge
  • Source: performance_schema.events_statements_summary_by_digest
  • Labels: schema, query

Replication metrics​

mysql_replication_io_status​

  • Description: Whether the replication IO thread is running
  • Type: Gauge
  • Labels: source_server_id, source_server_uuid, state, last_error

mysql_replication_sql_status​

  • Description: Whether the replication SQL thread is running
  • Type: Gauge
  • Labels: source_server_id, source_server_uuid, state, last_error

mysql_replication_lag_seconds​

  • Description: Seconds behind master
  • Type: Gauge
  • Labels: source_server_id, source_server_uuid

Connection metrics​

mysql_connections_max​

  • Description: Maximum number of allowed connections
  • Type: Gauge
  • Source: SHOW GLOBAL VARIABLES (max_connections)

mysql_connections_current​

  • Description: Current number of connected threads
  • Type: Gauge
  • Source: SHOW GLOBAL STATUS (Threads_connected)

mysql_connections_total​

  • Description: Total number of connections since server start
  • Type: Counter
  • Source: SHOW GLOBAL STATUS (Connections)

mysql_connections_aborted_total​

  • Description: Total number of aborted connection attempts
  • Type: Counter
  • Source: SHOW GLOBAL STATUS (Aborted_connects)

Traffic metrics​

mysql_traffic_received_bytes_total​

  • Description: Total bytes received by the server
  • Type: Counter
  • Source: SHOW GLOBAL STATUS (Bytes_received)

mysql_traffic_sent_bytes_total​

  • Description: Total bytes sent by the server
  • Type: Counter
  • Source: SHOW GLOBAL STATUS (Bytes_sent)

mysql_queries_total​

  • Description: Total number of queries executed
  • Type: Counter
  • Source: SHOW GLOBAL STATUS (Questions)

mysql_slow_queries_total​

  • Description: Total number of slow queries
  • Type: Counter
  • Source: SHOW GLOBAL STATUS (Slow_queries)

mysql_top_table_io_wait_time_per_second​

  • Description: Time spent on table I/O operations
  • Type: Gauge
  • Source: performance_schema.table_io_waits_summary_by_table
  • Labels: schema, table, operation

Change tracking​

When --track-database-changes is enabled, the agent detects and emits change events for:

  • Schema changes — The agent periodically snapshots the DDL of every table (columns, indexes, foreign keys) across all databases by querying information_schema. When a table's DDL changes between consecutive snapshots, a change event is emitted with a unified diff.
  • Settings changes — The agent snapshots all SHOW GLOBAL VARIABLES values each cycle. When a variable changes (e.g., after a SET GLOBAL or restart), a change event is emitted with the diff.

Each change event includes db.system, db.target, db.name, db_change.object, and db_change.type attributes.

Size metrics​

The agent collects database and table size metrics from information_schema.tables. For table sizes, only the top 20 largest tables across all databases are reported.

mysql_database_size_bytes​

  • Description: Total size of the database in bytes, computed as the sum of data_length + index_length for all tables
  • Type: Gauge
  • Source: information_schema.tables
  • Labels: db

mysql_table_size_bytes​

  • Description: Total size of the table in bytes (data_length + index_length)
  • Type: Gauge
  • Source: information_schema.tables
  • Labels: db, table

mysql_table_size_growth_bytes_per_second​

  • Description: Table size growth rate in bytes per second. Only the top 20 fastest growing tables across all databases are reported. Requires at least two collection cycles to compute.
  • Type: Gauge
  • Source: Computed from consecutive information_schema.tables measurements
  • Labels: db, table

MongoDB​

mongo_up​

  • Description: Whether the MongoDB server is reachable or not
  • Type: Gauge

mongo_scrape_error​

  • Description: Whether a scrape error occurred
  • Type: Gauge
  • Labels: error, warning

mongo_info​

  • Description: The server info
  • Type: Gauge
  • Labels: server_version

mongo_rs_status​

  • Description: Replica set status: 1 if the member is part of a replica set
  • Type: Gauge
  • Labels: rs, role

mongo_rs_last_applied_timestamp_ms​

  • Description: Timestamp of the last applied operation in milliseconds
  • Type: Gauge

Change tracking​

When --track-database-changes is enabled, the agent detects and emits change events for:

  • Index changes — MongoDB is schemaless, so instead of DDL the agent tracks indexes per collection. Each cycle it snapshots all indexes (name and key fields) for every collection. When indexes are added, removed, or modified, a change event is emitted with a unified diff.
  • Settings changes — The agent snapshots all server parameters via getParameter: "*" each cycle. When a parameter changes (e.g., after setParameter or a restart), a change event is emitted with the diff.

MongoDB system databases (admin, config, local) are always excluded from index tracking.

Each change event includes db.system, db.target, db.name, db_change.object, and db_change.type attributes.

Size metrics​

The agent collects database and collection size metrics. For collection sizes, only the top 20 largest collections across all databases are reported. MongoDB system databases (admin, config, local) are always excluded.

mongo_database_size_bytes​

  • Description: Total size of the database in bytes
  • Type: Gauge
  • Source: listDatabases command (sizeOnDisk)
  • Labels: db

mongo_collection_size_bytes​

  • Description: Total size of the collection in bytes (data + indexes + storage overhead)
  • Type: Gauge
  • Source: collStats command (totalSize)
  • Labels: db, collection

mongo_collection_size_growth_bytes_per_second​

  • Description: Collection size growth rate in bytes per second. Only the top 20 fastest growing collections across all databases are reported. Requires at least two collection cycles to compute.
  • Type: Gauge
  • Source: Computed from consecutive collStats measurements
  • Labels: db, collection

FluxCD​

The agent's embedded kube-state-metrics reads FluxCD custom resources (source.toolkit.fluxcd.io, kustomize.toolkit.fluxcd.io, helm.toolkit.fluxcd.io, fluxcd.controlplane.io) and exposes their state. This requires the agent's service account to have get/list/watch access to those API groups, which the Coroot Operator grants automatically.

Every metric below also carries uid, name, and namespace labels identifying the source custom resource. The *_info metrics are info-style: their value is always 1 and the useful data is carried in labels. The *_status metrics expose Kubernetes status conditions: one series per condition, with the value 1 when the condition holds (status: "True") and 0 otherwise ("False"/"Unknown").

fluxcd_git_repository_info / fluxcd_oci_repository_info / fluxcd_helm_repository_info​

  • Description: Information about a GitRepository / OCIRepository / HelmRepository source
  • Type: Info
  • Source: the source spec
  • Labels: url, interval, suspended

fluxcd_git_repository_status / fluxcd_oci_repository_status / fluxcd_helm_repository_status​

  • Description: Status conditions of a GitRepository / OCIRepository / HelmRepository source
  • Type: Gauge
  • Source: status.conditions[]
  • Labels: type (condition type, e.g. Ready), reason

fluxcd_helm_release_info​

  • Description: Information about a HelmRelease
  • Type: Info
  • Source: the HelmRelease spec
  • Labels: suspended, interval, target_namespace, source_kind, source_name, source_namespace, chart, version, chart_ref_kind, chart_ref_name, chart_ref_namespace

fluxcd_helm_release_status​

  • Description: Status conditions of a HelmRelease
  • Type: Gauge
  • Source: status.conditions[]
  • Labels: type, reason

fluxcd_helm_chart_info​

  • Description: Information about a HelmChart
  • Type: Info
  • Source: the HelmChart spec
  • Labels: chart, version, source_kind, source_name, source_namespace, interval, suspended

fluxcd_helm_chart_status​

  • Description: Status conditions of a HelmChart
  • Type: Gauge
  • Source: status.conditions[]
  • Labels: type, reason

fluxcd_kustomization_info​

  • Description: Information about a Kustomization
  • Type: Info
  • Source: the Kustomization spec and status
  • Labels: suspended, interval, path, source_kind, source_name, source_namespace, target_namespace, last_applied_revision, last_attempted_revision

fluxcd_kustomization_status​

  • Description: Status conditions of a Kustomization
  • Type: Gauge
  • Source: status.conditions[]
  • Labels: type, reason

fluxcd_kustomization_inventory_entry_info​

  • Description: A resource managed by a Kustomization (one series per inventory entry)
  • Type: Info
  • Source: status.inventory.entries[]
  • Labels: entry_id

fluxcd_kustomization_dependency_info​

  • Description: A dependency declared by a Kustomization (one series per dependsOn entry)
  • Type: Info
  • Source: spec.dependsOn[]
  • Labels: depends_on_name, depends_on_namespace

fluxcd_resourceset_info​

  • Description: Information about a ResourceSet
  • Type: Info
  • Source: the ResourceSet status
  • Labels: last_applied_revision

fluxcd_resourceset_status​

  • Description: Status conditions of a ResourceSet
  • Type: Gauge
  • Source: status.conditions[]
  • Labels: type, reason

fluxcd_resourceset_inventory_entry_info​

  • Description: A resource managed by a ResourceSet (one series per inventory entry)
  • Type: Info
  • Source: status.inventory.entries[]
  • Labels: entry_id

fluxcd_resourceset_dependency_info​

  • Description: A dependency declared by a ResourceSet (one series per dependsOn entry)
  • Type: Info
  • Source: spec.dependsOn[]
  • Labels: depends_on_kind, depends_on_name, depends_on_namespace

ArgoCD​

The agent's embedded kube-state-metrics reads ArgoCD Application resources (argoproj.io/v1alpha1) and exposes their sync, health, and operation state. This requires the agent's service account to have get/list/watch access to the argoproj.io API group, which the Coroot Operator grants automatically.

Every metric below also carries uid, name, and namespace labels identifying the Application. All of these are info-style metrics: their value is always 1 and the meaningful state is carried in labels (such as sync_status), so a status that ArgoCD doesn't currently report simply has no series.

argocd_application_info​

  • Description: Information about an Application
  • Type: Info
  • Source: the Application spec and status
  • Labels: project, source_type, repo, path, chart, target_revision, dest_server, dest_name, dest_namespace, revision

argocd_application_sync_status​

  • Description: Sync status of an Application
  • Type: Info
  • Source: status.sync.status
  • Labels: sync_status (e.g. Synced, OutOfSync, Unknown)

argocd_application_health_status​

  • Description: Health status of an Application
  • Type: Info
  • Source: status.health.status
  • Labels: health_status (e.g. Healthy, Progressing, Degraded, Suspended, Missing, Unknown)

argocd_application_operation_status​

  • Description: Phase of the most recent sync operation
  • Type: Info
  • Source: status.operationState.phase
  • Labels: operation_phase (e.g. Running, Succeeded, Failed, Error, Terminating)

argocd_application_operation_finished_timestamp_seconds​

  • Description: When the most recent sync operation finished, as a Unix timestamp
  • Type: Gauge
  • Source: status.operationState.finishedAt

argocd_application_resource_info​

  • Description: A resource managed by an Application (one series per resource)
  • Type: Info
  • Source: status.resources[]
  • Labels: resource_group, resource_kind, resource_namespace, resource_name

argocd_application_resource_sync_status​

  • Description: Sync status of a managed resource
  • Type: Info
  • Source: status.resources[].status
  • Labels: resource_group, resource_kind, resource_namespace, resource_name, sync_status

argocd_application_resource_health_status​

  • Description: Health status of a managed resource
  • Type: Info
  • Source: status.resources[].health.status
  • Labels: resource_group, resource_kind, resource_namespace, resource_name, health_status

argocd_application_resource_status​

  • Description: Result for a resource from the most recent sync operation
  • Type: Info
  • Source: status.operationState.syncResult.resources[]
  • Labels: resource_group, resource_kind, resource_namespace, resource_name, status (e.g. Synced, Pruned, SyncFailed)
Looking for 24/7 support from the Coroot team? Subscribe to Coroot Enterprise:Start free trial