Connect the signals behind every build

The data model

A Bazel build may contain one or more invocations. Hermetiq links build and invocation identity to targets, actions, tests, cache events, profiles, remote actions, and configured infrastructure telemetry.

Bazel Build Event Protocol

BEP is the primary build-event stream. It supplies build and invocation identity, command and timing information, targets, test results, build status, and metadata emitted by Bazel.

Remote cache events

Cache telemetry supports hit-rate analysis and action-level investigation. Where miss analysis is available, Hermetiq can distinguish reasons such as changed inputs, commands, environments, platforms, first-seen actions, and instance mismatches.

Cache availability and detail depend on the cache integration and the events received for the project.

Completed remote actions

Completed-action data connects each remote action to timing and execution context, including available queue, input-fetch, execution, output-upload, worker, command, and cost fields.

For Buildbarn deployments, Hermetiq can combine action data with configured scheduler, worker, storage, and Kubernetes telemetry for infrastructure investigation.

Bazel JSON profiles

JSON trace profiles add phase timing, critical-path actions, action parallelism, memory and client-pressure signals, and profile-derived insights. Enable the recommended profile flags and configure CAS read access so Hermetiq can retrieve the profile artifact.

Infrastructure and cost

Hermetiq can use configured metrics, logs, traces, and cost sources to relate build behavior to Buildbarn, Kubernetes, cloud resources, and supporting services. Exact availability depends on the hosted or customer-managed deployment and the integrations enabled there.