What the Chat Agent can do v1.4.0 (LTS)

Suggest edits

Chat Agent helps you operate Hybrid Manager (HM) in plain language, grouped by HM area. Available capabilities depend on the configured model's strength tier — see Model strength tiers. All capabilities respect your HM permissions and project scope — see Security and data handling.

HM documentation Q&A

Answer conceptual or how-to questions about HM, including model serving, Lakehouse Analytics, and migrations. Answers come from a snapshot of the official HM documentation that ships with each HM release. Chat Agent cites the pages it read. If Chat Agent can't find an answer in the bundled snapshot, it says so and points you to the official EDB Hybrid Manager documentation site, where you can check for content added after this release.

Try:

  • How are log files controlled in HM?
  • What are commit scopes in PGD and when should I use them?

Manage estate, projects, users, and roles

Browse and manage the HM estate, projects, organization and project users, role assignments, and activity feeds. You can't delete users or configure identity providers with Chat Agent — use Configuring IdPs in the HM console for IdP setup.

Try:

  • List the projects.
  • Add the Editor role to alice@example.com on project payments.

Postgres cluster lifecycle management

List, inspect, create, delete, and restore Postgres clusters in these topologies: Single Node, High Availability (HA), and Distributed High Availability (DHA). Restore supports point-in-time recovery (PITR) and targeted-database restore. Chat Agent inspects backups and lists supported Postgres image versions. Long-running actions run as background tasks — Chat Agent returns a task reference and can check progress.

Try:

  • I want to create a small Postgres cluster for development.
  • Restore cluster orders-prod from the latest backup, and name the new cluster orders-restored.

Cluster monitoring, alerts, and observability

Get current or historical values of standard cluster metrics. Available metrics cover CPU, memory, storage, I/O, throughput, network, connections, transactions, query rate and latency, buffer cache hit ratio, top databases, write-ahead logs, and checkpoints. Render metrics over time as charts. View active alerts per cluster or per project. Chat Agent mirrors the Cluster Monitoring page in the HM console. It doesn't create or modify dashboards, acknowledge alerts, or silence alerts — use the HM console for those.

Try:

  • Plot CPU usage on customers-prod over the past 24 hours.
  • How is storage usage on my cluster customers-prod?

Kubernetes workload observability

Inspect the Kubernetes workloads behind your clusters through HM's observability stack. Query pod and namespace metrics from Prometheus, read logs through Loki, and list the available Grafana data sources.

Try:

  • Tail the recent errors in namespace p-0hrzzicgpq-a.

Recommendations and advisories (read-only)

Get configuration, indexing, statistics, and security recommendations for a cluster, plus aggregated health scores across a project. Chat Agent surfaces the recommendations for review — apply them from the HM console.

Try:

  • Are there any pending index recommendations on orders-prod?
  • Summarize the security recommendations for cluster orders-prod.

Cluster health reports

List, fetch, analyze, and compare cluster health reports. HM generates one report per cluster per day — newly created clusters have no reports for the day of creation.

Try:

  • Compare yesterday's and today's health reports for customers-prod and tell me what changed.

Schema design recommendations

Get table-level recommendations for data types, normalization, indexing, partitioning, and constraints. Chat Agent reads the table's structure and the top resource-consuming queries recorded against it (from pg_stat_statements), then applies a Postgres and EDB best-practices catalog. With no recorded query activity, recommendations fall back to schema-only fixes from the table definition.

Try:

  • Suggest schema improvements for table public.orders on customers-prod, database app.

Browse Lakehouse Analytics catalogs (read-only)

List and inspect the Iceberg and Lakehouse catalogs registered in your projects. Create, update, and delete catalogs from the HM console.

Try:

  • List the Iceberg catalogs.

AI Factory inventory (read-only)

Browse the AI Factory resources in your projects — registered models, inference services, knowledge bases, pipelines, and flows. Chat Agent lists and inspects these resources. Create and configure them from the HM console.

Try:

  • List my inference services
  • List my knowledge bases in project payments.

Usage analytics

Review aggregated resource-usage analytics for your organization and projects — the compute hours, memory, and storage your Postgres clusters consume — including period-over-period comparison. Usage covers resource consumption only, not cost.

Try:

  • How much compute and storage did we use this month across the org?
  • Show the resource usage for project payments this month, broken down by cluster.

Data Migration Service (read-only)

View existing migrations, sources, destinations, table mappings, error history, and assessment reports. To start, pause, resume, or delete migrations, use the HM console — Chat Agent points you to the right page.

Try:

  • Show me the failing migrations in project migrations-prod and the most recent error for each.

Oracle-to-Postgres SQL translation

Translate Oracle SQL to EDB Postgres-compatible SQL. Useful when preparing queries or schema definitions ahead of a migration from Oracle.

Try:

  • Translate this Oracle SQL: SELECT NVL(name, 'unknown') FROM customers …

General constraints

These rules apply to every capability:

  • HM-only scope. Off-topic questions (general knowledge, math, other products) are out of scope.
  • Confirmation gates. Create, update, delete, drop, DDL, and DML operations require an explicit yes before execution.
  • Permission-honest. On a permission-denied error, Chat Agent stops and reports the error rather than retrying or routing around it.
  • Status comes from a status check. Listing a resource doesn't imply it's healthy or active — Chat Agent calls a status endpoint when needed.

For the security model behind these guarantees, see Security and data handling.

See also

← Prev

EDB Hybrid Manager Chat Agent

↑ Up

EDB Hybrid Manager Chat Agent

Next →

Configuring the Chat Agent