How can I accurately measure Bazel build performance to identify bottlenecks?

When working with large Bazel workloads, understanding where time is spent during a build can be challenging because the tool aggregates actions across multiple platforms and caches results.

Developers often need a reliable way to collect granular timing data for individual rules, sandbox executions, and remote cache hits without interfering with normal builds.

What metrics should be enabled, how can they be isolated from caching effects, and which visualization approaches help pinpoint slow steps?