# Working with Sentry

You open Sentry from the project overview, read issues with stack trace and frequency, and check after each release which errors are new.

> Source: https://www.application-platform.com/en/docs/working-with-sentry/

## Opening Sentry from the platform

The prerequisite is that a Sentry connection is stored under **Connections** and enabled for the component under **Features**; [Error tracking]({{< relref "error-tracking" >}}) describes how. Then open the **project overview** and click the **Sentry** tile. It leads to the component's Sentry project in your Sentry organization, in Sentry Cloud or in your own instance. If the tile is missing, Sentry is not yet enabled for that component.

Apps, homepages, and backends can each have their own Sentry project. An error in the backend and an error in the app therefore land in different Sentry projects, even though both belong to the same platform project.

## Reading issues

Sentry groups similar errors into one issue instead of listing every single occurrence separately. For each issue you see the stack trace and the release version in which the error occurred, how often it happened and when it was last seen, and the environment, such as production. When deciding what to fix first, frequency and last occurrence are the most useful indicators: an error that keeps happening weighs more than one that has not appeared since the last release.

## Checking after a release

After each production release, a brief look into the Sentry project pays off. Sentry groups issues by release version, so you can see at a glance which errors have appeared since the release. [Git workflow]({{< relref "git-workflow" >}}) describes how a release reaches production.