BEP provides the structured record of what Bazel attempted and what happened. Hermetiq ingests that event stream, correlates it with execution and infrastructure telemetry, and makes the result usable by engineers and AI agents.
Use Bazel’s structured event graph as the build record.
Build and target outcomes
Test results and failure history
Structured invocation metadata
Evidence shared with dashboards and MCP clients
Questions Hermetiq helps answer
Answer outcome questions from BEP—and know when another signal is required.
BEP describes the build events Bazel emitted. Hermetiq preserves that structure and connects optional profiles, actions, and infrastructure evidence only when the investigation needs them.
Command outcome
What authoritative command result and exit status did Bazel report for the invocation?
Target outcome
Which target, configuration, or aspect completed or failed?
Test evidence
Which test attempt, shard, or run failed, and which referenced artifacts were reported?
Data coverage
Which evidence is present, and which additional source is needed to answer the question?
Integration model
Send one build first; add deeper telemetry only when the question requires it.
The dashboard Quickstart generates the project-specific Build Event Service values. A successful first build should produce an invocation record before additional sources are connected.
01
Configure the Build Event Service
Use the endpoint and project values generated by the Hermetiq dashboard Quickstart.
02
Send one Bazel build
Verify that the invocation, requested targets, timing, command outcome, and—when tests run—test results reported by Bazel appear in the project.
03
Add deeper evidence when needed
Connect a compatible JSON profile, cache events, completed actions, or infrastructure telemetry for timing, cache, and RBE questions.
Product evidence
Use BEP for outcomes; use compatible profile data for critical-path analysis.
Failure recurrence
Inspect failed-action counts by mnemonic and recurring failure keys across recorded invocations.
Critical-path analysis
Inspect the chain that determined elapsed time when a compatible Bazel JSON trace profile—not BEP alone—is available.
Evidence model
Map each answer to the Bazel event that supports it.
Build outcome
BuildFinished provides the authoritative completion and exit status reported for the invocation.
Target outcome
TargetComplete records completion for a target, configuration, and aspect when Bazel emits it.
Test outcome
TestResult records individual test attempts, shards, and runs and can reference logs or other outputs.
Additional context
Profiles, cache events, completed actions, and infrastructure signals attach deeper evidence to the BEP-anchored invocation.
Technical references
Verify the underlying telemetry and performance model.