Skip to content
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.

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

Bump sentry-sdk from 1.6.0 to 1.17.0 #343

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 22, 2023

Bumps sentry-sdk from 1.6.0 to 1.17.0.

Release notes

Sourced from sentry-sdk's releases.

1.17.0

Various fixes & improvements

  • New: Monitor Celery Beat tasks with Sentry Cron Monitoring.

    With this feature you can make sure that your Celery beat tasks run at the right time and see if they where successful or not.

    Warning Cron Monitoring is currently in beta. Beta features are still in-progress and may have bugs. We recognize the irony. If you have any questions or feedback, please email us at crons-feedback@sentry.io, reach out via Discord (#cronjobs), or open an issue.

    Usage:

    # File: tasks.py
    from celery import Celery, signals
    from celery.schedules import crontab
    import sentry_sdk
    from sentry_sdk.crons import monitor
    from sentry_sdk.integrations.celery import CeleryIntegration
    1. Setup your Celery beat configuration
    app = Celery('mytasks', broker='redis://localhost:6379/0')
    app.conf.beat_schedule = {
    'set-in-beat-schedule': {
    'task': 'tasks.tell_the_world',
    'schedule': crontab(hour='10', minute='15'),
    'args': ("in beat_schedule set", ),
    },
    }
    2. Initialize Sentry either in celeryd_init or beat_init signal.
    #@​signals.celeryd_init.connect
    @​signals.beat_init.connect
    def init_sentry(**kwargs):
    sentry_sdk.init(
    dsn='...',
    integrations=[CeleryIntegration()],
    environment="local.dev.grace",
    release="v1.0.7-a1",
    )
    3. Link your Celery task to a Sentry Cron Monitor

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

1.17.0

Various fixes & improvements

  • New: Monitor Celery Beat tasks with Sentry Cron Monitoring.

    With this feature you can make sure that your Celery beat tasks run at the right time and see if they where successful or not.

    Warning Cron Monitoring is currently in beta. Beta features are still in-progress and may have bugs. We recognize the irony. If you have any questions or feedback, please email us at crons-feedback@sentry.io, reach out via Discord (#cronjobs), or open an issue.

    Usage:

    # File: tasks.py
    from celery import Celery, signals
    from celery.schedules import crontab
    import sentry_sdk
    from sentry_sdk.crons import monitor
    from sentry_sdk.integrations.celery import CeleryIntegration
    1. Setup your Celery beat configuration
    app = Celery('mytasks', broker='redis://localhost:6379/0')
    app.conf.beat_schedule = {
    'set-in-beat-schedule': {
    'task': 'tasks.tell_the_world',
    'schedule': crontab(hour='10', minute='15'),
    'args': ("in beat_schedule set", ),
    },
    }
    2. Initialize Sentry either in celeryd_init or beat_init signal.
    #@​signals.celeryd_init.connect
    @​signals.beat_init.connect
    def init_sentry(**kwargs):
    sentry_sdk.init(
    dsn='...',
    integrations=[CeleryIntegration()],
    environment="local.dev.grace",
    release="v1.0.7-a1",
    )

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [sentry-sdk](https://github.com/getsentry/sentry-python) from 1.6.0 to 1.17.0.
- [Release notes](https://github.com/getsentry/sentry-python/releases)
- [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-python@1.6.0...1.17.0)

---
updated-dependencies:
- dependency-name: sentry-sdk
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants