Skip to content

Bump sentry-sdk[flask] from 1.29.2 to 1.30.0

Johannes Zumthurm requested to merge dependabot/pip/sentry-sdk-flask--1.30.0 into master

Created by: dependabot[bot]

Bumps sentry-sdk[flask] from 1.29.2 to 1.30.0.

Release notes

Sourced from sentry-sdk[flask]'s releases.

1.30.0

Various fixes & improvements

  • Officially support Python 3.11 (#2300) by @​sentrivana

  • Context manager monitor (#2290) by @​szokeasaurusrex

  • Set response status code in transaction response context. (#2312) by @​antonpirker

  • Add missing context kwarg to _sentry_task_factory (#2267) by @​JohnnyDeuss

  • In Postgres take the connection params from the connection (#2308) by @​antonpirker

  • Experimental: Allow using OTel for performance instrumentation (#2272) by @​sentrivana

    This release includes experimental support for replacing Sentry's default performance monitoring solution with one powered by OpenTelemetry without having to do any manual setup.

    Try it out by installing pip install sentry-sdk[opentelemetry-experimental] and then initializing the SDK with:

    sentry_sdk.init(
    # ...your usual options...
    _experiments={"otel_powered_performance": True},
)

    This enables OpenTelemetry performance monitoring support for some of the most popular frameworks and libraries (Flask, Django, FastAPI, requests...).

    We're looking forward to your feedback! Please let us know about your experience in this discussion: https://github.com/getsentry/sentry/discussions/55023

    Important note: Please note that this feature is experimental and in a proof-of-concept stage and is not meant for production use. It may be changed or removed at any point.

  • Enable backpressure handling by default (#2298) by @​sl0thentr0py

    The SDK now dynamically downsamples transactions to reduce backpressure in high throughput systems. It starts a new Monitor thread to perform some health checks which decide to downsample (halved each time) in 10 second intervals till the system is healthy again.

    To disable this behavior, use:

    sentry_sdk.init(
    # ...your usual options...
    enable_backpressure_handling=False,
)

... (truncated)

Changelog

Sourced from sentry-sdk[flask]'s changelog.

1.30.0

Various fixes & improvements

  • Officially support Python 3.11 (#2300) by @​sentrivana

  • Context manager monitor (#2290) by @​szokeasaurusrex

  • Set response status code in transaction response context. (#2312) by @​antonpirker

  • Add missing context kwarg to _sentry_task_factory (#2267) by @​JohnnyDeuss

  • In Postgres take the connection params from the connection (#2308) by @​antonpirker

  • Experimental: Allow using OTel for performance instrumentation (#2272) by @​sentrivana

    This release includes experimental support for replacing Sentry's default performance monitoring solution with one powered by OpenTelemetry without having to do any manual setup.

    Try it out by installing pip install sentry-sdk[opentelemetry-experimental] and then initializing the SDK with:

    sentry_sdk.init(
    # ...your usual options...
    _experiments={"otel_powered_performance": True},
)

    This enables OpenTelemetry performance monitoring support for some of the most popular frameworks and libraries (Flask, Django, FastAPI, requests...).

    We're looking forward to your feedback! Please let us know about your experience in this discussion: https://github.com/getsentry/sentry/discussions/55023

    Important note: Please note that this feature is experimental and in a proof-of-concept stage and is not meant for production use. It may be changed or removed at any point.

  • Enable backpressure handling by default (#2298) by @​sl0thentr0py

    The SDK now dynamically downsamples transactions to reduce backpressure in high throughput systems. It starts a new Monitor thread to perform some health checks which decide to downsample (halved each time) in 10 second intervals till the system is healthy again.

    To disable this behavior, use:

    sentry_sdk.init(
    # ...your usual options...
    enable_backpressure_handling=False,
)

... (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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Merge request reports