Skip to content

Commit

Permalink
Problem: Sentry reporting didn't have release information
Browse files Browse the repository at this point in the history
Solution : Add the release number to sentry init according
to the Sentry documentation
https://docs.sentry.io/platforms/python/configuration/releases/
  • Loading branch information
olethanh committed Oct 22, 2024
1 parent 123a4d8 commit d1831b3
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion src/aleph/vm/orchestrator/cli.py
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@
from aleph.vm.conf import ALLOW_DEVELOPER_SSH_KEYS, make_db_url, settings
from aleph.vm.models import VmExecution
from aleph.vm.pool import VmPool
from aleph.vm.version import get_version_from_apt, get_version_from_git
from aleph.vm.version import __version__, get_version_from_apt, get_version_from_git

Check warning on line 23 in src/aleph/vm/orchestrator/cli.py

View check run for this annotation

Codecov / codecov/patch

src/aleph/vm/orchestrator/cli.py#L23

Added line #L23 was not covered by tests

from . import metrics, supervisor
from .pubsub import PubSub
Expand Down Expand Up @@ -325,6 +325,7 @@ def main():
# of transactions for performance monitoring.
# We recommend adjusting this value in production.
traces_sample_rate=1.0,
release=__version__,
)
sentry_sdk.set_context(
"version",
Expand Down

0 comments on commit d1831b3

Please sign in to comment.