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

Support of opentelemetry v1.4 for django and celery instrumentations #626

Closed
zawi99 opened this issue Aug 25, 2021 · 3 comments
Closed

Support of opentelemetry v1.4 for django and celery instrumentations #626

zawi99 opened this issue Aug 25, 2021 · 3 comments

Comments

@zawi99
Copy link

zawi99 commented Aug 25, 2021

Some time ago opentelemetry-python released a new version (1.4) which supports OTLP Exporter Protobuf over HTTP. I'd really like to use this feature with opentelemetry-instrumentation-django and opentelemetry-instrumentation-celery, however there is a problem. Both packages requires opentelemetry-api in version 1.3.

# setup.cfg

install_requires =
    opentelemetry-api ~= 1.3

My questions:

  • is there a plan to bump those dependencies versions?
  • if not, what are the obstacles/caveats to do it?
@zawi99 zawi99 changed the title Support of opentelemetry v1.4 for django and celery instrumentation Support of opentelemetry v1.4 for django and celery instrumentations Aug 25, 2021
@srikanthccv
Copy link
Member

That shouldn't be a problem https://www.python.org/dev/peps/pep-0440/#compatible-release. Did you have any issue installing these packages?

@owais
Copy link
Contributor

owais commented Aug 27, 2021

    opentelemetry-api ~= 1.3

This means it requires any version newer than or equal to 1.3 but older than 2.0. This is working as intended so I'm closing this but please re-open if there is another related issue with dependencies.

@owais owais closed this as completed Aug 27, 2021
@zawi99
Copy link
Author

zawi99 commented Aug 30, 2021

Thank you for the explanation.
In version 0.22b0 setup.cfg there is opentelemetry-api == 1.3.0 as dependency. Sorry, it was my mistake not providing current state. In higher versions i.e. 0.23b0+ there is already correct identifier used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants