Skip to content

docs(release-health): Simplify markup by removing unnecessary HTML #16465

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jaffrepaul merged 2 commits into from
Feb 19, 2026
Merged

docs(release-health): Simplify markup by removing unnecessary HTML #16465

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
509c7c4
docs(release-health): Simplify markup by removing unnecessary HTML
jaffrepaul Feb 19, 2026
689cd85
Apply suggestions from code review
jaffrepaul Feb 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 14 additions & 34 deletions docs/product/releases/health/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,45 +30,25 @@ Sentry distinguishes between two kinds of sessions:

### User-Mode/Application-Mode Sessions

<ul>
A user- or application-mode session begins with the start of the application.
Or, it begins with bringing the already started application back from
background to the foreground. In this context, a user is defined by one or
more of the following: a unique ID or UUID, username, or email.

<li style={{listStyleType:'none'}}>
A user- or application-mode session begins with the start of the application.
Or, it begins with bringing the already started application back from
background to the foreground. In this context, a user is defined by one or
more of the following: a unique ID or UUID, username, or email.
</li>

<br></br>

<li style={{listStyleType:'none'}}>
This type of session ends with the closing of the application or with the
application being sent to the background. If the application is in the
background for less than 30 seconds, we do not start the session again.
Applications that are active even on the background (for example, a music
player) should track the sessions manually for the background process.
</li>

</ul>
This type of session ends with the closing of the application or with the
application being sent to the background. If the application is in the
background for less than 30 seconds, we do not start the session again.
Applications that are active even on the background (for example, a music
player) should track the sessions manually for the background process.

### Server-Mode/Request-Mode Sessions

<ul>

<li style={{listStyleType:'none'}}>
Server- or request-mode sessions roughly correspond to HTTP requests or RPC
calls in a server setting. A session is started when the server receives a
request, and terminates when the server sends a response.
</li>

<br></br>

<li style={{listStyleType:'none'}}>
These are typically high in volume since each session corresponds to a single
request.
</li>
Server or request-mode sessions roughly correspond to HTTP requests or RPC
calls in a server setting. A session is started when the server receives a
request, and terminates when the server sends a response.

</ul>
These are typically high in volume since each session corresponds to a single
request.

Sessions, whether application-mode or request-mode, are submitted to Sentry so you can track the usage and adoption of your application. When a user of your application experiences a crash, error, or abnormal exit, the session will be flagged accordingly, and Sentry calculates derived metrics. The metrics include data such as the number of users that didn't experience a crash in the specified time range.

Expand Down
Loading