Skip to content

fix: Clarify error level impact on sessions #15198

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
merged 7 commits into from
Oct 16, 2025
Merged

fix: Clarify error level impact on sessions #15198

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
e7f4b28
fix: Clarify error level impact on sessions
philipphofmann Oct 14, 2025
f198f61
Refine session error tracking logic
cursoragent Oct 14, 2025
616d474
Refine session error tracking logic
cursoragent Oct 14, 2025
394469f
Update session error tracking documentation
cursoragent Oct 14, 2025
ad899c4
reword
philipphofmann Oct 14, 2025
09a2697
Merge branch 'master' into fix/session-error-level
philipphofmann Oct 15, 2025
a5ef22f
add table
philipphofmann Oct 15, 2025
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
25 changes: 24 additions & 1 deletion develop-docs/sdk/telemetry/sessions/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -271,7 +271,7 @@ not report any more session updates or start a new session.

SDKs are encouraged to distinguish between different ways of ending a session:

- `exited`: this means the session ended cleanly. It's is the same as the
- `exited`: this means the session ended cleanly. It's is the same as the
session staying in `ok` from the point of success reports. However only
sessions ending in `exited` will be considered for session durations.
A session is allowed to go to `exited` even if errors occurred.
Expand Down Expand Up @@ -314,6 +314,29 @@ count of greater than zero is considered an errored session. All crashed and
abnormal sessions are also at all times considered errored but subtracted from
the final errored session count.

Only events that stem from `captureException`, `captureError`, or `captureEvent`
must increment the `errors` counter when their level is `error` or higher. As SDKs
set the default level to `error` for these methods, a level lower than `error`
means the users changed it manually. This gives the users the ability to capture
error events not marking sessions as errored. `captureEvent` is included because
users might manually create exception events with it. Events stemming from
`captureMessage` must not affect the session's error count, regardless of their
log level. For all methods, it doesn't matter if the event has a stack trace or not.
The following table summarizes the behavior of the methods:

| method | level | increments `errors` counter |
| --- | --- | --- |
| captureException / captureError | `fatal` | `yes` |
| captureException / captureError | `error` | `yes` |
| captureException / captureError | `warning` | `no` |
| captureEvent | `fatal` | `yes` |
| captureEvent | `error` | `yes` |
| captureEvent | `warning` | `no` |
| captureMessage | `fatal` | `no` |
| captureMessage | `error` | `no` |
| captureMessage | `warning` | `no` |


### Exited

A session can transition to `exited` which is exactly the same state as `ok`
Expand Down
Loading