Service pages#

This page covers the service-level controls exposed in the DUMB Frontend, including auto-restart policies, auto-update scheduling, and configuration editors.

Overview#

Each service page includes:

• Current status, health, and restart counters
• Start, stop, and restart actions (except for the API service)
• Configuration editors with validation
• Log viewers (service logs, plus special logs when available)
• Embedded UI tab when supported and enabled
• Dependency graph view for core/dependency startup relationships
• Per-service auto-restart overrides
• On-demand update checks and auto-update scheduling
• Seerr Sync controls when viewing a Seerr instance
• Symlink Job Center (for symlink-capable services) with active jobs, recent history, retry, and failure clearing
• Sidebar operator QoL controls (quick filters, saved views, compact mode, and command palette)

Status and controls#

The header shows the service name, status dot, and health badge. When auto-restart is enabled for a service, you also see restart counters and the last restart reason. With Geek Mode enabled, the header also displays the internal config key and process name in monospace.

Action buttons:

• Start, Stop, Restart for the current service
• Auto-restart opens per-service overrides (if supported)

Dependency graph view#

On the DUMB Config tab, use the Dependencies action to open a pop-out dependency graph panel that:

• Shows dependency startup order for the current service context
• Highlights missing/stopped dependencies
• Provides remediation suggestions
• Offers one-click Fix now actions to start available dependency processes
• Links to this documentation section from the panel header

Notes:

• For multi-instance dependency services (for example rclone, zurg), the graph scopes dependencies to instances linked to the current core service via core_service/core_services. Instance-scoped conditional dependencies are filtered so that only the specific instance associated with the current service is shown -- for example, "Rclone w/ CLID" only shows its specific Zurg instance, not Zurg instances belonging to other rclone configurations.
• If no linked dependency instance exists, the panel reports that mapping gap instead of treating an unrelated instance as valid.
• The panel also infers links from service config relationships (core_service, core_services, wait_for_url, wait_for_dir) so service-specific relationships (for example Seerr, Tautulli, Arr instances tied to Decypharr/NzbDAV/AltMount, or optional access services) can show real dependency edges.
• Dependency resolution runs on the backend (GET /api/process/dependency-graph) so startup ordering and dependency edges are aligned with backend process/config semantics.
• The dependency graph surfaces conditional startup dependencies from the backend startup ordering logic. These are dependencies that only apply when specific services are enabled -- for example, Prowlarr depends on Sonarr/Radarr only when those are enabled; Tautulli depends on Plex only when Plex is enabled; NeutArr depends on arr services only when use_neutarr is enabled on those instances. These appear with the conditional_startup_map signal and are styled the same as other hard runtime dependencies.
• Each dependency edge displays its signal type as a colored badge tag with a tooltip explaining the signal. Signal types include:
  • Hard runtime (orange): core map, conditional startup, wait for url/dir/mounts, rclone provider, non-core dep
  • Hard configured (cyan): core service fields
  • Soft linkage (gray): optional integration, documented integration
• The dependency pop-out supports scope selection:
  • Runtime: hard runtime/configured dependencies
  • All: includes soft linkage edges (for example optional integrations and documented service integrations like Seerr request routing to Sonarr/Radarr)
• The Flow view renders a Mermaid dependency graph (with edge strength styling) and shows directed edge details.
• The Flow view also lists backend parallel_groups to make concurrent prerequisite stages explicit (for example Riven startup prerequisites in parallel before backend start).
• With Geek Mode enabled:
  • A Copy JSON button copies the full dependency graph API response to the clipboard
  • A latency badge shows the fetch time in milliseconds next to the panel title
  • The Flow view also shows the raw Mermaid graph source text for troubleshooting

For dependency services (for example zurg/rclone), the panel also shows which core services currently depend on them.

Process Metrics panel#

With Geek Mode enabled, the DUMB Config tab displays a Process Metrics panel showing live data from the /api/metrics endpoint:

Click Refresh to re-fetch metrics on demand. Metrics are fetched once when entering a service page with Geek Mode active.

Auto-restart policy#

Configure the global auto-restart behavior:

The auto-restart modal includes a contextual Why this matters callout linking to this section.

Service overrides#

Service pages can also override auto-restart settings per service:

• Enable/disable auto-restart for the current service
• Override defaults (intervals, thresholds, backoff)
• Apply in memory or save to file

Auto-update settings#

The updates panel lets you check for updates on demand and configure automatic update checks.

DUMB also shows global update notices in the frontend when a DUMB backend or DUMB frontend update is available, blocked, or was recently applied. The notice opens a review dialog with the affected service, current and available versions, the update message, and a release-notes link when the service has a known repository URL. The first release with this feature also seeds a one-time informational notice with the current version; production versions link to release notes, DUMB dev-image versions such as v2.4.2-dev.5 link to the rolling dev-build reference, and branch builds with commit markers link to the relevant commit. Applied and informational notices are recorded by the backend under /config/update_notices.json, while dismissed notices are remembered only in the current browser.

The panel includes a contextual Why this matters callout linking to this section.

Manual update actions:

• Check for updates runs a one-time update check even if auto-update is disabled.
• Install update applies the latest available update when allowed.
• Override + install appears when a service is pinned to a release/branch and you explicitly choose to bypass the block.

Automatic update settings:

Notes:

• Saving auto-update settings reschedules the updater immediately (no service restart required).
• Next check is shown in the panel once auto-update is enabled and scheduled.

Seerr Sync panel#

On Seerr service pages, the Seerr Sync panel lets you:

• Configure the top-level seerr_sync settings (enable, polling, external primary/subordinates)
• Toggle sync behavior options (pending/approved/declined/deletes/4K)
• Select the per-instance sync_role (disabled/primary/subordinate)
• Test external primary/subordinate connections before saving
• View sync status and failed requests
• Review a contextual Why this matters callout linking to this section

API keys are hidden by default and can be revealed when needed.

Failed request lists are shown in a scrollable panel so large queues don’t expand the page.

Configuration editors#

The frontend includes editors for the main DUMB config and service-specific configs.

Edit DUMB Config#

View or edit dumb_config.json. Changes can be saved in memory or written to disk.

Notes:

• The editor runs schema validation when available.
• Invalid JSON or validation errors block saves until corrected.
• Validation errors include inline "Why invalid" guidance (for example missing required fields, wrong types, unknown keys).
• A live config diff preview shows added/changed/removed paths before apply/save.
• Risk-tagged config changes (for example command/env/path/network/restart/update/credential fields) require an explicit acknowledgement checkbox before apply/save.

Edit Service Config#

For services with separate config files, you can open and modify those settings here. Service configs should be saved to file.

Logs#

Service pages include log viewers when a log file is configured or when the service is allowlisted for logs:

• Filter by text and level
• Limit displayed lines
• Follow tail and refresh on an interval (including custom intervals)
• Manual refresh
• Download logs

Special log tabs#

• Traefik Access Logs appear on the Traefik service page.
• DBRepair Logs appear on the Plex service page when DBRepair is enabled.

Embedded UI#

When embedded UIs are enabled and the service exposes a UI, a dedicated Embedded UI tab appears.

Features:

• Open in new tab (only shown for local/private access)
• Full window toggle
• UI path selector for services with multiple entry points (for example Zilean)

NzbDAV uses a trailing slash in its embedded UI path to match its frontend routing.

Default tab selection#

You can choose a default tab for each service page (for example, always open logs). The selection is stored in the UI preferences.

Sidebar operator QoL#

The services sidebar includes faster navigation controls for large stacks:

• Quick filters for All, Running, Stopped, and Unhealthy services
• Search filter for process name/config key matching
• Saved views to store and re-apply filter/search/toggle combinations
• Compact mode to reduce service-row density in the sidebar
• Command palette (Ctrl/Cmd + K) to jump directly to service pages
• Assignable service shortcuts configured from command-palette results by entering shortcut-capture mode and pressing the combo
• Collapsible Sidebar tools section to keep controls hidden when not needed

These controls are persisted in dumb_config.json under dumb.ui.sidebar (with local state used as a fallback during initial load) and are intended for power-user workflows across many services.

The same sidebar preference block also includes persisted dashboard tile ordering at:

• dumb.ui.sidebar.service_order

Tile order is written from dashboard drag-and-drop actions and then consumed by both the dashboard and the sidebar service list.

Related pages#

• Settings - Preferences and onboarding controls
• Dashboard - Service controls and logs