diff --git a/maintenance-ops/self-hosting/diagnostics.mdx b/maintenance-ops/self-hosting/diagnostics.mdx
index 28b662b0..be4c7f78 100644
--- a/maintenance-ops/self-hosting/diagnostics.mdx
+++ b/maintenance-ops/self-hosting/diagnostics.mdx
@@ -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 |