"Discarded session update because of missing release"

[jgillard]

How do you use Sentry?

Sentry Saas (sentry.io)

Version

2.23.1

Steps to Reproduce

Updating from 2.22.0 to 2.23.1 when release is not set starts logging this line: "Discarded session update because of missing release" when this was not logged before.

sentry-python/sentry_sdk/client.py

Line 945 in be22912

if not session.release:

Expected Result

The log line is not seen, or it is seen and it's clearer what to do with it.

Actual Result

I'm not clear on what to do next here. I see in the docs that Sentry tries to infer a release if it's not explicitly set in sentry_sdk.init(), and it seems that's not possible with our current setup. Now I see this new log line but am not clear about whether it's causing any issues or not. Do we need to find a away to set the release, or can this be ignored? We've never noticed any issues related to releases before. I didn't find anything in the release notes about this so assume it was an unintentional change.

[szokeasaurusrex]

Hi @jgillard, you can safely ignore this log message if everything else appears to be working as expected; we should only be showing it if you start the SDK in debug mode by passing debug=True to sentry_sdk.init. Version 2.23.0 introduced a regression where users who set custom root log handler/log level would see the Sentry SDK debug logs even when debug mode was disabled.

We are fixing this regression in version 2.26.0 of the SDK, which we will release shortly. In the meantime, feel free to ignore this message, and any other logs you are getting from the SDK. We apologize for any confusion that this regression caused.