Connect the signals behind every build
Understand what Hermetiq receives from Bazel, remote cache, Buildbarn, profiles, OpenTelemetry, and configured cost sources.
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.
Build History, invocation detail, target and test context, result links, and the event record other telemetry attaches to.
Your project’s Quickstart-generated Bazel configuration.
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.
For Buildbarn, connect the Action Cache lookup event feed and enable cache-event ingestion for the project. Configure authorized Content Addressable Storage (CAS) read access to enrich those events with action commands, inputs, environments, and platform properties.
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.
Configure Buildbarn’s completed-action logger to send records to the Hermetiq ingestion endpoint supplied for your deployment, and enable completed-action ingestion for the project. These records supply remote timing and resource evidence beyond the Bazel event stream.
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.
Review profile configuration →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.
Connect Prometheus-format Buildbarn and Kubernetes metrics through your observability pipeline. Configure the query backend and namespace labels so Hermetiq can resolve worker, scheduler, storage, and service health.
Forward Buildbarn pod logs and Kubernetes events, then configure authorized queries with the namespace and pod labels needed to find the relevant records.
Provide authorized read access to the deployment’s namespace for workload configuration, worker pools, replica counts, and autoscaling state.
OpenTelemetry traces from instrumented services and pipelines.
Configure a reachable OpenCost API and enable the cost-report integration. Verify cluster coverage, allocation windows, and attribution labels; cost data does not populate from BEP alone.
These integrations are optional and depend on deployment configuration and permissions. Confirm cost-report availability with Hermetiq; connecting OpenCost alone does not enable every cost view.
Review integration prerequisites →