Monitoring and Logs
This guide covers checking Mydia's health, wiring up a Docker health check, and viewing logs.
Health Checks
Mydia exposes a health endpoint:
Docker Health Check
services:
mydia:
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:4000/health"]
interval: 30s
timeout: 10s
retries: 3
Logs
View container logs:
Configure log level:
Background Jobs
Most of what Mydia does on your behalf (scans, metadata refreshes, download monitoring, imports) runs as a background job rather than in a request. When something is not happening and the logs are quiet, Admin > Background Jobs shows the queues, what is running, and what failed.
Next Steps
- Updating Mydia - what to watch in the logs during an upgrade
- Backing Up and Restoring - what the automatic pre-migration copy does and does not cover
- Managing Libraries - when a scan finds nothing, the path is the usual culprit
- Environment Variables -
LOG_LEVELand the rest