Skip to content
DiscVaultDiscVault Docs

Admin: Logs, jobs, and security

Goal and result

Section titled “Goal and result”

Monitor health, logs, operations, background jobs, plugin failures, and account security.

Applies to

Section titled “Applies to”

Stable and beta use the same v26 service names and endpoints. Logs can contain titles and user identifiers; redact them before sharing.

DiscVault v26 stable

Section titled “DiscVault v26 stable”
  • DiscVault v26 stable · ghcr.io/helmerznl/discvault:latest
  • same API + worker + MCP + PostgreSQL diagnostics

DiscVault v26 beta

Section titled “DiscVault v26 beta”
  • DiscVault v26 beta · ghcr.io/helmerznl/discvault:beta
  • same API + worker + MCP + PostgreSQL diagnostics

Prerequisites

Section titled “Prerequisites”
  • owner access
  • matching backup set
  • timestamped logs with private data redacted

Procedure

Section titled “Procedure”
  1. Inspect: /api/next/health · Compose status
  2. Inspect: timestamped logs with private data redacted · failed job ID
  3. Verify: latest matched backup · secret exposure
  4. Preserve: error + timestamp + image digest · before retry

Commands and settings

Section titled “Commands and settings”

Both channels

Section titled “Both channels”
Terminal window
docker compose --env-file /opt/discvault/.env -p discvault -f /opt/discvault/compose.yaml logs --tail=200 next-api next-worker next-mcp postgres
curl --fail http://localhost:6080/api/next/jobs
curl --fail http://localhost:6080/api/next/health

Expected result

Section titled “Expected result”

Health succeeds, failed jobs have an actionable error, backups are current, and no default or exposed secret remains.

  • one failing layer is isolated with its timestamp, status, image digest, and redacted error
  • matching backup set

Safety and rollback

Section titled “Safety and rollback”

Next step

Section titled “Next step”

Troubleshooting

Source and status

Section titled “Source and status”