Per-backend forward → commit Storage-Commitment funnel to each backend Router this instance forwards to

Queue Health load per pool — the routing family SynthIQ balances

Destination Health per-backend heartbeat + queue + disk

No commitment-confirmed transactions in this window yet.

No commitment-confirmed transactions in this window yet.

No routing events in this window yet. Drive any C-STORE traffic through the SynthIQ SCP to populate.

Fleet Overview

Per-Router Snapshot

Queue Depth Timeline processing (solid) + outbound (dashed)

Other SynthIqConfig values from appsettings.json below are read-only. To change them, edit appsettings.Production.json on the host and restart the service.

Configuration Backup & Migration

Export the full configuration (pools, SMTP, watermark, study-cache, disk-monitor, auth policy) as a JSON file for backup or migration, or import a previously exported file. Secrets are redacted by default (re-entered on import from the running config); tick "Include credentials" to export them passphrase-encrypted for a full cross-host clone. LDAP connection settings are host-configured and not part of this backup.

Authentication

Session lifetime + account lockout policy. SynthIQ always requires login; toggling auth off is a deploy-time appsettings.json concern, not an operator-runtime control. LDAP/AD accounts follow Active Directory Group Policy and are not affected by the Max Login Attempts setting (Phase 3 will add the LDAP card).

Storage-Commit Listener

The dedicated DICOM listener for Storage Commitment (N-EVENT-REPORT) reverse-associations from backend Routers. Changes are saved immediately but apply to the running listener on the next SynthIQ restart (the listener binds once at startup).

LDAP / Active Directory

When enabled, the login flow tries the local SynthIQ user store first; on miss, it falls through to LDAP/AD. Test Bind is on the Roles & LDAP page.