Operations Dashboard

Operations Dashboard

Builds that include the local operations dashboard expose it at /operations for signed-in users. Open it from the activity icon in the dashboard header.

The page reads the local database and does not send telemetry or diagnostic data elsewhere. Raw errors, marketplace URLs, notification destinations, tokens, and credentials are excluded.

What the cards mean

• Tracker shows the age of the worker's last successful heartbeat and latest error event.
• Scan queue shows pending, running, failed, and overdue product checks.
• Notifications shows verified channels, pending deliveries, and sent or failed deliveries from the previous 24 hours.
• Storage & backup shows database size, price observations, observations added during the last 24 hours, and the latest backup recorded by Prizen's backup script.

Green means healthy, amber needs attention, red requires action, and gray means Prizen does not yet have enough data. Large figures use compact notation: 1K, 12.5K, 2.3M, and 4B. The displayed figure may be rounded; stored data is not changed.

Backup freshness becomes known only after scripts/backup-release.sh completes successfully. Backups made by other tools cannot be detected by the dashboard.

Safe local update

For the repository's development Compose stack:

podman compose build migrate app
podman compose run --rm --no-deps migrate
podman compose up -d --no-deps app

This applies additive migrations and recreates the app without deleting the PostgreSQL volume. Do not use down --volumes, down -v, or remove named volumes during an update.

If a card needs attention, inspect local state and logs:

podman compose ps
podman compose logs --tail=200 tracker app db

For implementation details and thresholds, see the repository reference.