← all services
chat-agent 4 endpoints
Endpoint-level X-ray over the last 3d — 12 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 chat-agent
Neo4j footprint
24
1.2 per request · 0 slow
owner · on-call
Sambasiva Bandarupalli
backup Ahmed Aburaed · CODEOWNERS /data-science/
| Endpoint | Calls ▾ | Avg latency | Max | Err % |
|---|---|---|---|---|
| GET /api/v1/threads | 6 | 110 ms | 217 ms | 0.0% |
| GET /api/v1/chat/:id/state | 3 | 139 ms | 233 ms | 33.3% |
| GET /api/v1/threads/:id | 2 | 238 ms | 361 ms | 0.0% |
| GET /api/v1/chat/:id/runs/:id/stream | 1 | 55 ms | 55 ms | 100.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.