Hi team,
I'm currently using azure-monitor-opentelemetry in a project that also relies on the opentelemetry-instrumentation-aiohttp, httpx, and requests libraries. However, I'm unable to upgrade past version 0.52b1 of those instrumentations because azure-monitor-opentelemetry has them pinned.
These versions are several months old now, and since then there have been multiple releases with important bug fixes and improvements in the OpenTelemetry ecosystem.
Can you please update the version constraints - either bump to at least 0.56b0 or allow a looser version spec (e.g., >=0.52b1, <0.57)?
Let me know if there's a compatibility or stability reason for the current pinning.
Thanks!
Hi team,
I'm currently using
azure-monitor-opentelemetryin a project that also relies on theopentelemetry-instrumentation-aiohttp,httpx, andrequestslibraries. However, I'm unable to upgrade past version0.52b1of those instrumentations becauseazure-monitor-opentelemetryhas them pinned.These versions are several months old now, and since then there have been multiple releases with important bug fixes and improvements in the OpenTelemetry ecosystem.
Can you please update the version constraints - either bump to at least
0.56b0or allow a looser version spec (e.g.,>=0.52b1, <0.57)?Let me know if there's a compatibility or stability reason for the current pinning.
Thanks!