← all services
feedsvc 7 endpoints
Endpoint-level X-ray over the last 48h — 92 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 · 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 feedsvc
last deploy
—
no ArgoCD sync recorded
Neo4j footprint
367
1.1 per request · 4 slow
owner · on-call
not declared
feedsvc is in no CODEOWNERS folder X-ray reads — the leads get it
| Endpoint | Calls ▴ | Avg latency | Max | Err % |
|---|---|---|---|---|
| GET /studies/:id/feed/cards/doc_ready/items | 1 | 410 ms | 410 ms | 0.0% |
| GET /studies/:id/feed/cards/edl_proposal/items | 1 | 309 ms | 309 ms | 0.0% |
| GET /studies/:id/feed/cards/wo_email/items | 1 | 419 ms | 419 ms | 0.0% |
| GET /studies/:id/feed/done | 1 | 0 ms | 0 ms | 100.0% |
| GET /studies/:id/feed/week | 9 | 3 ms | 15 ms | 100.0% |
| GET /studies/:id/feed | 17 | 62 ms | 138 ms | 47.1% |
| GET /studies/:id/feed/badge | 62 | 88 ms | 379 ms | 9.7% |
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.