Skip to content

Sentry lack INCEpTION's version #5977

@torgeirl

Description

@torgeirl

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:

  1. Manually set version in settings.properties (and updated it after each upgrade), ie:
sentry.release=40.2
  1. 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:
Image

Transcation metadata without workaround:
Image

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions