Use the following commands when Netpicker Support requests logs.
Check container status
docker compose ps
Collect logs from all containers
Last 30 minutes:
docker compose logs --since 30m --timestamps > netpicker_logs.log 2>&1
Last hour:
docker compose logs --since 1h --timestamps > netpicker_logs.log 2>&1
Specific time range:
docker compose logs \
--since "2026-08-31T08:00:00" \
--until "2026-08-31T08:30:00" \
--timestamps \
> netpicker_logs.log 2>&1
Collect logs from one container
Example for api:
docker logs api --since 30m --timestamps > api.log 2>&1
Or with Docker Compose:
docker compose logs api --since 30m --timestamps > api.log 2>&1
Replace api with the required container name.
Common troubleshooting scenarios
| Issue | Logs to collect |
| Backup/readout problem | kibbitzer |
| API unhealthy | api |
| Agent unhealthy | agent |
| Scheduled job problem | celery |
| Automation problem | api celery kibbitzer |
| GUI problem | frontend api |
| File transfer problem | transferium kibbitzer |
| Database problem | db pgbouncer api |
| Unknown issue | All containers |
Examples:
Backup problem
docker compose logs kibbitzer --since 30m --timestamps > kibbitzer.log 2>&1
Scheduler problem
docker compose logs celery api --since 1h --timestamps > scheduler_logs.log 2>&1
File transfer problem
docker compose logs transferium kibbitzer --since 1h --timestamps > transfer_logs.log 2>&1
Follow logs live
docker compose logs -f api
Multiple containers:
docker compose logs -f api celery kibbitzer
Press Ctrl+C to stop viewing the logs.
Last lines only
docker logs --tail 100 --timestamps api
When reproducing an issue
Note the current time:
date
Reproduce the issue and then collect logs, for example:
docker compose logs --since 10m --timestamps > netpicker_logs.log 2>&1
When sending logs to Netpicker Support, also provide:
- Approximate time of the issue
- Timezone
- Device name/IP, if applicable
- Job, backup, rule, or automation involved
- Whether the execution was manual or scheduled