When running a workload with telemetry enabled (e.g. in dsb_hotel example), the number of requests made by the workload generator does not match the number of traces found in Jaeger.
e.g. running a complex workload with 97 rps produces 963 requests, but only 881 traces in Jaeger. Adding a 5-second delay before exiting the workload loop (i.e. after the line
|
// Print statistics from the workload |
) brings the counts back into sync.
When running a workload with telemetry enabled (e.g. in dsb_hotel example), the number of requests made by the workload generator does not match the number of traces found in Jaeger.
e.g. running a complex workload with 97 rps produces 963 requests, but only 881 traces in Jaeger. Adding a 5-second delay before exiting the workload loop (i.e. after the line
blueprint/examples/dsb_hotel/cmplx_workload/workloadgen/workload.go
Line 97 in 8ce9074