Skip to content
Postgram

Queue Monitoring

Enrichment and extraction run asynchronously and can accumulate while models or DB load degrade.

What this page covers

Section titled “What this page covers”

How to monitor queue depth, failures, and stale work.

Core workflow

Section titled “Core workflow”
  1. Check queue from CLI:
Terminal window
pgm queue
  1. Check queue from REST:
Terminal window
curl http://127.0.0.1:3100/api/queue?include_failures=true \
  -H "Authorization: Bearer $PGM_API_KEY"
  1. Include failure context:
  • pending/completed/failed counts for extraction and embedding
  • recent failure messages and paths when include_failures=true
  1. For deeper operational view, query direct SQL:
Terminal window
./bin/pgm-admin sql "SELECT extraction_status, COUNT(*) FROM entities GROUP BY 1"

Notes

Section titled “Notes”
  • failure_limit defaults to 20 with a maximum of 100 when requesting include_failures=true.
  • If pending stays high, check worker startup and the relevant provider: embeddings for searchability, extraction only when graph extraction is enabled.