Describe the bug
When monitored by Sentry INCEpTION's version should be attached to both issues and transactions. It currently isn't so unless some workaround is applied release history isn't available in the Sentry.
Workarounds
There aresome ways of working around this issue:
- Manually set version in
settings.properties (and updated it after each upgrade), ie:
- Read
/srv/inception/version, pass its content to Sentry using the JAVA_OPTS -Dsentry.release, and restart an extra time (so the file's content gets updated) after each upgrade.
Screenshots
Transcation metadata with workaround:

Transcation metadata without workaround:

Please complete the following information:
- Version and build ID: 40.2, build b3b6b32
- OS: Linux
- Sentry monitoring is enabled by providing DSN etc in
settings.properties as described in docs.
Describe the bug
When monitored by Sentry INCEpTION's version should be attached to both issues and transactions. It currently isn't so unless some workaround is applied release history isn't available in the Sentry.
Workarounds
There aresome ways of working around this issue:
settings.properties(and updated it after each upgrade), ie:/srv/inception/version, pass its content to Sentry using theJAVA_OPTS-Dsentry.release, and restart an extra time (so the file's content gets updated) after each upgrade.Screenshots

Transcation metadata with workaround:
Transcation metadata without workaround:

Please complete the following information:
settings.propertiesas described in docs.