A slow remote build can come from the scheduler, the worker fleet, the network, storage, an execution platform, or the build graph itself. Hermetiq connects those layers so operators can act on the right one.
Separate a slow remote build into decisions operators can act on.
Hermetiq connects the build, action, and infrastructure evidence required to distinguish workload changes from queue, worker, transfer, and storage pressure.
Action phases
How much time did completed actions spend queueing, fetching inputs, executing, and uploading outputs?
Capacity pressure
Which worker or platform queue is saturated, and which builds are creating demand?
Workload cost
Which action types and targets are driving CPU time, wall time, and configured execution cost?
Regression point
What changed between comparable builds when latency or cost moved?
Integration model
Connect Bazel, completed actions, and the infrastructure that ran them.
Client-visible remote time is useful, but phase and capacity diagnosis requires matching action and infrastructure evidence.
01
Connect Bazel build events
Use BEP to establish invocation identity, configuration, targets, timing, and outcomes.
02
Add completed remote actions
Connect the available action records so queue, transfer, execution, worker, and outcome fields can be analyzed.
03
Add infrastructure context
Connect Buildbarn scheduler, worker, storage, and cost telemetry where configured, then compare equivalent workloads.
Product evidence
Move from aggregate remote time to the action and fleet evidence beneath it.
Remote action phases
Inspect individual action phases with worker and configured cost context when those fields are available.
Remote execution trends
Follow action volume, queue and wall time, CPU, fleet, and configured cost across recorded builds.
Evidence model
Tie each conclusion to the execution layer that produced it.
Completed-action timing
Queue, input-fetch, execution, and output-upload conclusions come from the phase fields reported for completed actions.
Bazel linkage
BEP connects action and infrastructure behavior to the invocation, configuration, targets, and outcome.
Infrastructure state
Scheduler, worker, storage, and platform-queue claims require the corresponding Buildbarn or OpenTelemetry signals.
Cost attribution
Cost views depend on completed work and the cost inputs configured for the deployment.
Technical references
Verify the underlying telemetry and performance model.