Konduo Manual

English

한국어

English

한국어

Appearance

PostgreSQL Plugin ​

The PostgreSQL plugin registers PostgreSQL servers as Konduo resources and connects connection, replication, vacuum, lock, transaction, and query activity signals to the operator UI.

Highlights ​

  • Collects server state and operational snapshots with read-only SQL queries.
  • Supports both Prometheus mapping packs and Konduo-managed PostgreSQL metric collection.
  • Focuses dashboards on availability evidence, connection pressure, transaction age, lock activity, replication lag, and cache/write behavior.
  • Separates diagnostics for connectivity, permissions, metric coverage, replication, and bloat/vacuum risk.

Before Registration ​

  • Prepare PostgreSQL host, port, database, username, password, and TLS settings.
  • Use a least-privilege account that can run the required read-only diagnostic queries.
  • Tune timeouts for managed collection so diagnostic queries do not add unexpected load.

Operations Tips ​

  • Review connection pressure together with max connection settings.
  • Interpret replication lag with primary/replica role, WAL receiver state, and apply delay.
  • For long transactions, lock waits, and delayed vacuum, read diagnostic snapshots together with metric trends.

PostgreSQL Enterprise Overlay ​

The PostgreSQL Enterprise overlay adds MCP descriptors, advanced diagnostics, log evidence mapping, metric mapping, and anomaly rules to PostgreSQL resources. It summarizes session, lock, connection, replication, storage, and vacuum state as operator evidence.

Highlights ​

  • Provides database info, monitoring overview, connectivity checks, diagnostics, topology, and metric mapping through MCP.
  • Includes session, lock, connection, configuration, replication, and storage/vacuum evidence in diagnostics.
  • Connects PostgreSQL diagnostics to an Enterprise log source through log evidence mapping.
  • Evaluates PostgreSQL logical metrics through declarative metric anomaly rules.

Before Registration ​

  • Community PostgreSQL connectivity and read permissions must be healthy.
  • Prepare Prometheus postgres exporter mapping and an OpenSearch log source when log evidence is needed.
  • Confirm topology read permissions for replication and failover planning context.

Operations Tips ​

  • Interpret lock waits, connection saturation, and replication lag together with application deployments and vacuum state.
  • Failover descriptors provide planning and inventory context; actual state changes need separate authorization and audit boundaries.