Most production errors are never reported. People reload and move on. What reaches the team is a fraction, often days later: “It didn’t work yesterday.”
Whether that happened once or four hundred times since the last release stays a guess until something writes it down. Sentry can do that. The friction is rarely the tool – it is the setup. That is the part the platform takes over.
Sentry after you connect it
The platform sets Sentry up for your project — no integration to assemble by hand, no checklist to repeat for every new project.
One condition applies: Sentry is only configured when the project has its own connection stored, so your error data lives in your organisation rather than a shared account. The form also supports a host mode for self-hosted instances.
Errors appear where you already work
Production errors are visible inside the platform, filtered by repository. Each entry carries the stack trace, release and context — the details that let you understand a failure instead of first reproducing it.
When you need to go deeper, a link takes you to the detail view in Sentry — a deliberate step rather than the only way to learn something is broken at all.
Signing in to your Sentry organisation
After you connect Sentry, the platform sets up single sign-on into that Sentry organisation. People sign in there with the same platform account they already use (email and password, or a passkey). That is not a third way to sign in to the platform itself, and it is not a Sentry hosted by the platform. A link in your profile goes straight to the sign-in page of your Sentry organisation.
Versioned releases make errors attributable
Releases are versioned, and that version is attached to the error, so “when did this start?” turns into a question with an answer. If an error only appears from a certain version onwards, the cause narrows to that release rather than everything shipped over past weeks.
Monitoring comes next
Infrastructure monitoring is announced but not the operating baseline yet. Error tracking with Sentry is the channel for application errors today. Server health and monitoring data on the dashboard come later.
Related topics
Once the Sentry connection is in place, the platform takes care of the rest of the setup. Recurring groundwork gets automated once instead of redone in every project. The page on CI/CD automation describes what that looks like for building and shipping. For an overview of other services that can be connected, see the features page.
