Sentry
Baz can use Sentry as the observability source for the SRE agent.
Sentry is supported in the SRE-agent flow and can be used to surface production issues and open fix PRs in the mapped repositories.
Simple setup flow
Open the Sentry integration settings in Baz.
Enter your Sentry auth token.
Enter the Sentry base URL.
Enter the Sentry org slug.
Add the relevant Sentry project slugs.
Save the integration.
Make sure the relevant repositories are connected to Baz with write access.
Make sure sandbox is enabled for the repositories where Baz should open SRE PRs.
Enable the SRE agent for the org.
Add service-to-repository or project-to-repository mapping where needed so Baz can connect Sentry issues to the right codebase.
What Baz checks during setup
Baz validates that:
the credentials are valid
the Sentry workspace is reachable
the base URL is valid
If the setup is valid, Baz can use Sentry findings as input for the SRE flow.
Multi-project support
Sentry supports multiple projects per integration.
This is important for organizations that use a separate Sentry project for each service. In those cases, Baz should be configured with all relevant project slugs so the SRE agent can work across the full service set.
What is required for SRE PRs to work
A connected Sentry integration is only one part of the flow.
Baz also needs:
the target repositories connected in Baz
GitHub write access for those repositories
sandbox configured for those repositories
SRE agent enabled for the org
service-to-repository or project-to-repository mapping when Baz cannot resolve the target repository automatically
Common reasons it does not work
The Sentry credentials are invalid.
The base URL or org details are incorrect.
The required projects were not added.
The repositories are not connected with write access.
Sandbox is missing for the target repository.
The SRE agent is disabled for the org.
Baz cannot map the Sentry issue to the correct repository.
Last updated