← all services
chat-agent 4 endpoints
Endpoint-level X-ray over the last 48h — 6 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
26
1.3 per request · 1 slow
owner · on-call
Sambasiva Bandarupalli
backup Ahmed Aburaed · CODEOWNERS /data-science/
| Endpoint | Calls ▴ | Avg latency | Max | Err % |
|---|---|---|---|---|
| GET /api/v1/chat/:id/state | 1 | 231 ms | 231 ms | 0.0% |
| POST /api/v1/threads | 1 | 80 ms | 80 ms | 0.0% |
| GET /api/v1/threads | 2 | 152 ms | 198 ms | 0.0% |
| POST /api/v1/chat/:id/runs/stream | 2 | — | — | 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.