← all services
execsvc 3 endpoints
Endpoint-level X-ray over the last 24h — 3 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.50% derived · 0.0× burn
p95 vs normal
—
no baseline yet
open findings
0
nothing open for execsvc
last deploy
2d ago
automated ·
5beaa388Neo4j footprint
3
0.0 per request · 0 slow
owner · on-call
Madhava Mukkamala
backup Shashank Agrawal · CODEOWNERS /execsvc/
| Endpoint | Calls ▾ | Avg latency | Max | Err % |
|---|---|---|---|---|
| GET /api/trialexec/study/:id/actor | 1 | 1.28 s | 1.28 s | 0.0% |
| GET /api/trialexec/study/:id/site | 1 | 327 ms | 327 ms | 0.0% |
| GET /api/trialexec/v2/training/mine | 1 | 239 ms | 239 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.