← all services
docproc 6 endpoints
Endpoint-level X-ray over the last 3d — 134 API calls.
Endpoints are derived from the request logs and templatized (:id).
Click one for its Neo4j fan-out, traces, and logs (fetched live).
See the raw calls:
all API calls ·
failing (5xx) →
What it costs:
its bill · namespace tilda · requests vs use · its LLM calls · AI spend by org
error budget
healthy
99.90% derived · 0.0× burn
p95 vs normal
—
no baseline yet
last deploy
—
no ArgoCD sync recorded
Neo4j footprint
68k
65.4 per request · 345 slow
owner · on-call
Sambasiva Bandarupalli
backup Ahmed Aburaed · CODEOWNERS /data-science/
| Endpoint | Calls ▾ | Avg latency | Max | Err % |
|---|---|---|---|---|
| GET /api/v1/docproc/recommendations | 58 | 3.19 s | 9.60 s | 0.0% |
| GET /api/v1/docproc/ai-runs/:id | 31 | 91 ms | 323 ms | 0.0% |
| GET /api/v1/docproc/supported-languages | 21 | 52 ms | 106 ms | 0.0% |
| GET /api/v1/docproc/recommendations/screening/config | 18 | 68 ms | 257 ms | 0.0% |
| POST /api/v1/docproc/ai-runs | 5 | 1.36 s | 2.88 s | 0.0% |
| PUT /api/v1/docproc/recommendations/:id | 1 | 189 ms | 189 ms | 0.0% |
Per-endpoint Neo4j fan-out (and N+1 detection) is one click away on each endpoint's Queries tab — fetched live by sampling that endpoint's recent traces.