PrintStash v0.6.6: metrics, health checks, and Unraid

PrintStash v0.6.6 focused on operating the server: scrapeable metrics, more diagnostic health data, an Unraid installation path, and recovery for scans left running across a restart.

Prometheus metrics

The API exposed Prometheus text format at /metrics. Initial metrics covered HTTP request latency by route template, completed ingestion outcomes, and live printer status by provider.

The endpoint was open by default for a trusted internal network. Setting VAULT_METRICS_TOKEN required a static Bearer token from the scraper.

The current metric names and a minimal Prometheus configuration are in the monitoring guide.

More useful health output

/api/v1/health added background ingestion counts and shared-volume scan status. These joined the existing database, storage, backup, and printer-provider sections, making the endpoint more useful than a simple process-alive response.

Unraid templates

The repository gained Community Applications metadata, API and frontend XML templates, and an Unraid-specific setup guide. The install created a shared printstash Docker network, started the API before the frontend, and finished in the normal setup wizard.

The current sequence is documented in running PrintStash on Unraid.

Interrupted scans recover

If the backend stopped during a shared-volume scan, that scan could remain marked running after startup. The scheduler then skipped it indefinitely.

v0.6.6 reset orphaned running scans to an error state during startup. The next scheduled or manual scan could proceed normally.