1. Target
service-a
2. Basic
3. Exceptions
Each one ends up as a span event, an error log and an exception profile.
4. CPU and memory
Retained memory is kept until release; repeated calls end in an OOMKill.
5. Call chain
The target calls each hop in turn; mixing Java and .NET gives one trace across both.
6. Relay
service-a
ms
Waits up to 30 s per hop, 60 s in total. In VictoriaTraces each wait is the gap in a server span before its next client span; db adds INSERT/SELECT spans.
7. Database
INSERT a visit, run the slow query, SELECT the visits per service (PostgreSQL).
8. Browser
Only Faro sees these: they go to VictoriaLogs through Alloy, not to the services.
9. Load generator
req/s
s
Idle
10. Responses
| Time | Request | Status | ms | Trace |
|---|
No calls yet.