Skip to content

Diagnostics response includes service version and Sync Config source #716

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
benitav merged 2 commits into from
Oct 21, 2026
Merged

Diagnostics response includes service version and Sync Config source #716

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
63826c7
docs: add service.version and sync_config_source to Diagnostics response
mintlify[bot] Oct 21, 2026
ca3f395
Merge branch 'main' into autopilot/8826a7e4
benitav Oct 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions maintenance-ops/self-hosting/diagnostics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,12 +44,16 @@ curl -X POST http://localhost:8080/api/admin/v1/diagnostics \

The response `data` object contains:

**`service`**: information about the running PowerSync Service. `service.version` is the Service version, such as `1.27.1`.

**`connections`** — whether PowerSync can reach the configured source database and any connection-level errors.

**`active_sync_rules`** — the currently serving Sync Config (Sync Streams or Sync Rules). Contains a `connections[]` array with details about each replication connection including slot name, WAL status, and tables being replicated. Also includes an `errors[]` array for warnings or errors.

**`deploying_sync_rules`** — only present while a new Sync Config is being deployed and the initial replication is in progress. PowerSync runs this process in parallel so clients continue to be served by the existing active config. Once initial replication completes, this section disappears and `active_sync_rules` updates.

**`sync_config_source`**: where the Service gets its Sync Config. The value is `config` if the Sync Config is defined in the Service configuration, such as the `sync_config:` section of `service.yaml`. Otherwise, the value is `api`, and the Sync Config is deployed [via the API](/maintenance-ops/self-hosting/update-sync-rules#option-3-deploy-via-api).

Each connection in `active_sync_rules.connections[]` includes:

| Field | Description |
Expand Down
Loading