View all the projects associated with teams that you're a member of, then dive into their details quickly.

A Project represents your service or application in Sentry. For example, you might have separate projects for your API server and frontend client.

When you first create a project, you also assign a team to it. All members of the assigned team have access to the project. Additional teams can be added in [Project] > Settings > Project Teams.

You can create more projects to reflect your application landscape with finer granularity (for example, a separate project for each repo, mapping components and micro-services to the teams that own them). For most pages in Sentry, including Issues and Discover, the top-level filter bar defaults to showing information for your projects, so that you only see what's relevant to you and your team(s). How you set up your projects can go a long way in reducing noise and improving productivity. Learn more about best practices for setting up projects in our account setup documentation.

Projects differ from environments, which are designed to help triage issues, especially in a multi-staged release process.

The Projects page lists all the projects assigned to teams you're a member of. Projects are displayed in alphabetical order and with a high-level overview of the following:

  • A snapshot of both errors and transactions in the last 24 hours
  • The percentage of crash free sessions, if you have configured release health (not available for watchOS; no Mach exception support on tvOS)
  • Deploys, if you have configured your SDK to provide a release identifier and are tracking deploys

Tip: For faster access, star your favorite projects to move them to the top of the page.

Click on a project from the Projects page to open the Project Details page.

The Project Details page provides an overview of errors, performance, and the health of your releases. Use this page to quickly correlate spikes in error rates with the issues causing them, react to critical alerts, and analyze long-term trends.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").