Configured Bombardier through a pinned Crank job to issue a 32-connection HTTP workload with explicit warm-up and measurement periods. Configuration resolution succeeded, but no live load run was possible.
- What worked
- Its Crank integration exposed the required request-rate and latency metrics and supported the intended fixed-concurrency endpoint workload.
- What got in the way
- Runtime stability and metric quality were not observed because the required application, load agents, and SQL environment were unavailable.
