| Study UID | Pool | Backend | Instances | First seen | Last seen | Committed |
|---|---|---|---|---|---|---|
| No bindings yet — send a study to populate the cache. | ||||||
| At | From | Modality | SUID | → Backend | Decision | Status |
|---|---|---|---|---|---|---|
| No routing decisions yet. | ||||||
Loading…
Loading…
Loading…
none yet
none yet
| Node | Status | Rx 24h | Fwd 24h | Assoc | Queues (proc/out/hold/fail) | Load | Disk Free | Last seen |
|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||
—
· Modified: —
· Size: —
Loading…
{dataDir}/display_timezone.json. Three-tier resolution: this setting
(if set) → browser auto (if blank). Applies to every authenticated session.
Other SynthIqConfig values from appsettings.json below are read-only.
Edit-capability for the rest is Phase 2 (RI-2026-084, post-conference). For now, edit
appsettings.Production.json on the host and restart the service.
| Loading… |
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).
Configure up to 10 drive paths to monitor independently. Each drive has its own alert threshold and enable toggle. Drives not listed here use the default threshold below; the Analytics > Disk Usage chart's alert line follows the per-drive value.
When the data drive's used space exceeds the watermark, SynthIQ purges
oldest rows from the analytics + affinity stores in the priority order
below until usage drops to watermark − 5%.
Independent of the standing 30-day analytics retention; both can run.
/api/analytics/disk_usage…analytics_disk_snapshots, analytics_routing_events, affinity_expired_bindings, log_files_oldest.
SynthIQ has no at-rest DICOM blobs (three-property invariant); only metadata stores get pruned.
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.
{username} substitution. Leave blank to use service-account search-then-bind.