← all services
docproc 3 endpoints
Endpoint-level X-ray over the last 14d — 23 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
open findings
0
nothing open for docproc
last deploy
2d ago
automated ·
6db9855aNeo4j footprint
28k
2.4 per request · 54 slow
owner · on-call
Sambasiva Bandarupalli
backup Ahmed Aburaed · CODEOWNERS /data-science/
| Endpoint | Calls ▾ | Avg latency | Max | Err % |
|---|---|---|---|---|
| GET /api/v1/docproc/recommendations | 9 | 328 ms | 785 ms | 0.0% |
| GET /api/v1/docproc/supported-languages | 8 | 66 ms | 180 ms | 0.0% |
| GET /api/v1/docproc/recommendations/screening/config | 6 | 43 ms | 72 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.