Suspect Commits in Frontend Observability
Suspect Commits in Frontend Observability
When an error appears in your app, you want to know which code change caused it — without digging through git log. Suspect Commits in Frontend Observability now pins the exact commit your app was built from at the top of the candidate list on the error summary page, so you can go straight from a stack trace to the change that introduced it.
Just enable the new gitHash option on the Faro bundler plugin (@grafana/faro-webpack-plugin, @grafana/faro-rollup-plugin, @grafana/faro-esbuild-plugin, or @grafana/faro-metro-plugin), or set app.gitHash directly when initializing the Faro Web SDK and Frontend Observability does the rest.
The bundler plugin auto-detects the commit via git rev-parse HEAD, with an explicit override for CI environments where the local HEAD isn’t the SHA you want to track (multi-stage Docker builds, GitHub Actions pull_request events, and so on).
Existing errors aren’t affected — the commit hash is recorded the first time an error is seen against a build that carries it. See the documentation for the full setup and verification steps.
