Bazel Invocation Analyzer

Get free, personalized suggestions on how to improve the performance of Bazel builds and tests

Bazel collects performance data when it is invoked, but it is hard to understand. The Bazel Invocation Analyzer automates this process and provides concrete guidance on next steps to take.

You can analyze your Bazel profiles on analyzer.engflow.com or download the source code from GitHub and run the tool locally.

Open-source contributions

We welcome contributions to this project.

You can contribute to the code base or help by reporting bugs, requesting new features and providing feedback. Share the Bazel Invocation Analyzer with others who may find it helpful.

Ways to get in touch

  • Provide feedback through the Web UI on analyzer.engflow.com.
  • View the source code and issue tracking on GitHub.
  • You can also email the development team directly.

More about EngFlow’s platform

Search across builds

Stop hunting through pipelines and logs. Find similar failures, specific targets, specific tests, specific users, or specific time windows—then compare runs.

Time and performance attribution

See where time goes across the build graph: critical path, slow actions, queueing, downloads, remote execution, test time, and bottlenecks. Move from “it’s slow” to “this is the constraint.”

Explain any invocation

Inspect builds from developer machines and CI in the same interface. See what ran, what failed, what changed, and what artifacts were produced.

Failure forensics, not log reading

Drill into the first failing action, its inputs/outputs, execution context, and dependencies. Understand whether the failure is deterministic, environmental, or flaky.