Python instrumentation library for metrics #1934
Unanswered
overmeulen
asked this question in
Q&A
Replies: 3 comments 7 replies
-
looking into this... |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hello @overmeulen Sorry for the late reply. The development of the new metrics is still in prototype. Progress is being made in this PR. Right now this is changing very quickly as the metrics spec progresses. Do you need a workaround for your issue? |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
We're currently doing a POC in our company, using the metrics part of the python instrumentation library.
I know this part is still in alpha but we faced a problem that I wanted to share.
After running our python code for a few hours, the collector-agent to which we're sending our metrics enters an infinite loop of export errors because it's trying to send more than 4Mb of data in one shot which is the default limit with gRPC.
The root cause of the problem seems to come from the python library that keeps the last value of each metric (even if we don't emit those metrics anymore) and keep sending them to the collector with the rest at each collection interval.
https://github.com/open-telemetry/opentelemetry-python/blob/v1.10a0/opentelemetry-sdk/src/opentelemetry/sdk/metrics/__init__.py#L265
This explains why after some time I reach this 4Mb limit.
Note that in my case I only have cumulative metrics and I even configured the MeterProvider as stateless so I don't really need for the library to keep the last value...
Is the implementation of the missing feature (the TODO in the link) already planned ?
Do you have any visibility on the next releases of the metrics SDK ?
Thanks,
Olivier
Beta Was this translation helpful? Give feedback.
All reactions