Connecting Hybrid Manager or Loki v1

Register an EDB Hybrid Manager (HM) deployment or a standalone Grafana Loki endpoint — the legacy sources — to see AI agent sessions reconstructed from their Postgres query logs. On this path the viewer doesn't read aidb telemetry, so it shows the SQL each session ran but no agent identities or governance decisions. For a Postgres database running the aidb extension — the primary source — see Connecting an aidb database instead.

An instance is a registered upstream data source. The viewer can connect to multiple instances at the same time, aggregating clusters and sessions across all of them. Instance configuration, including access keys, is stored server-side and never sent to the browser.

Manage instances on the Configure page, accessible from the home page's Configure Instances button or from Settings → Configure instance in the header.

Understanding instance types

Choose the instance type that matches your source:

Adding an HM instance

Make sure the following is true for an HM instance to surface AI agent sessions:

• Postgres statement logging is enabled on the target clusters (log_statement = 'all' or log_min_duration_statement = 0).
• The cluster is reachable over the network from the viewer's backend.
• AI agent workloads run through Airman MCP with a declared purpose, so that activity is tagged and discoverable. See Configuring Airman MCP for how to set up purpose labels, access modes, and the Postgres roles that enforce governance boundaries.

You create the machine user API key in the HM admin portal. The viewer stores it server-side and never returns it to the browser. For more on credential handling, see Securing access and handling credentials.

1. Open the Configure Instances page.
2. Select Add New.
3. Complete the form:
   • Type — HM.
   • Name — A descriptive label, for example Production EU.
   • Base URL — The HM API endpoint, for example https://hm.example.com:8443.
   • Access Key — The machine user API key. These keys typically start with hmak_ or baak_.
4. Select Add Instance.

On success, the viewer's backend discovers projects and clusters from the HM instance, and those clusters appear on the home page within seconds.

Adding a Loki instance

Follow these steps to add a standalone Loki endpoint:

1. Open the Configure Instances page.
2. Select Add New.
3. Complete the form:
   • Type — Loki.
   • Name — A descriptive label, for example Dev Loki.
   • Base URL — The Loki HTTP endpoint, for example http://loki.internal:3100.
   • Authorization — Optional. A bearer token or other authorization header value, if your Loki endpoint requires one.
4. Select Add Instance.

For Loki instances, the viewer creates a single stub project and cluster, and all Loki sessions appear under it.

Removing an instance

Select the Delete button on an instance row on the Configure page to remove the instance. A confirmation popover appears. On confirmation, the viewer removes the instance record, its cached session data, and its sync watermarks.

Removal is irreversible. Re-adding the instance requires resyncing its history from upstream.

Resyncing an instance

Force a full resync when upstream data was corrected or backfilled, when the cache looks inconsistent, or when the cache database was lost. The backend caches session summaries for fast retrieval.

1. On the Configure page, locate the instance row.
2. Select the Resync button (the sync icon).
3. The backend clears the instance's cached data and begins a full background sync.

The instance shows its sync status as Syncing (with a spinner), Done (with a session count), or Error (with a message). The resync runs in the background, so you can continue using the viewer while it completes. For details on how syncing works, see Architecture and data flow.