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. Browser
Only Faro sees these: they go to Loki through Alloy, not to the services.
7. Load generator
req/s
s
Idle
8. Responses
| Time | Request | Status | ms | Trace |
|---|
No calls yet.