-
Notifications
You must be signed in to change notification settings - Fork 532
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
Add entry point for opentelemetry propagator #3085
Comments
mender
added a commit
to mender/sentry-python
that referenced
this issue
May 19, 2024
Add entry point for sentry_sdk.integrations.opentelemetry.SentryPropagator. This makes possible to configure opentelemetry using environment variables and add SentryPropagator to existing ones instead of replace them. Closes getsentry#3085
mender
added a commit
to mender/sentry-python
that referenced
this issue
May 19, 2024
Add entry point for sentry_sdk.integrations.opentelemetry.SentryPropagator. This makes possible to configure opentelemetry using environment variables and add SentryPropagator to existing ones instead of replace them. Closes getsentry#3085
Thank you for the issue and the PR @mender, we will take a look. |
mender
added a commit
to mender/sentry-python
that referenced
this issue
May 31, 2024
Add entry point for sentry_sdk.integrations.opentelemetry.SentryPropagator. This makes possible to configure opentelemetry using environment variables and add SentryPropagator to existing ones instead of replace them. Closes getsentry#3085
mender
added a commit
to mender/sentry-python
that referenced
this issue
Jun 10, 2024
Add entry point for sentry_sdk.integrations.opentelemetry.SentryPropagator. This makes possible to configure opentelemetry using environment variables and add SentryPropagator to existing ones instead of replace them. Closes getsentry#3085
mender
added a commit
to mender/sentry-python
that referenced
this issue
Jun 17, 2024
Add entry point for sentry_sdk.integrations.opentelemetry.SentryPropagator. This makes possible to configure opentelemetry using environment variables and add SentryPropagator to existing ones instead of replace them. Closes getsentry#3085
mender
added a commit
to mender/sentry-python
that referenced
this issue
Jun 23, 2024
Add entry point for sentry_sdk.integrations.opentelemetry.SentryPropagator. This makes possible to configure opentelemetry using environment variables and add SentryPropagator to existing ones instead of replace them. Closes getsentry#3085
arjennienhuis
pushed a commit
to arjennienhuis/sentry-python
that referenced
this issue
Sep 30, 2024
…3086) Add entry point for sentry_sdk.integrations.opentelemetry.SentryPropagator. This makes possible to configure opentelemetry using environment variables and add SentryPropagator to existing ones instead of replace them. Closes getsentry#3085 Co-authored-by: Neel Shah <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement
According to the documentation, the recommended way to integrate with OpenTelemetry is to completely replace existing propagators using
In case of distributed tracing it is not correct behaviour. We have to add the
SentryPropagator
to the existing ones instead. Opentelemetry provides environment variables as a most common way to configure it. However, propagators added via environment variables must be declared in entry points (ref). And here is an example of how entry points are declared in OpenTelemetry.Solution Brainstorm
I propose adding entry point for
SentryPropagator
in setup.py.The text was updated successfully, but these errors were encountered: