You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected to see a dump like that generated for the JavaScript SDK in dump-js.txt.
What is the actual behavior?
The generated exponential histogram in dump-python.txt seems to have the following problems:
There is a negative bucket, even though no negative values are added to the histogram. (This actually causes a downstream vendor to reject the histogram.)
All 160 buckets are provided even though the last 79 are all empty. Other SDKs (e.g. Javascript, dump-js.txt) trim unnecessary buckets, reducing the size of the payload.
Additional context
None.
The text was updated successfully, but these errors were encountered:
This produces a dump file (dump-corrected-python.txt) that has no negative buckets and the positive buckets include only the lowest, non-zero buckets.
There is some overhead in searching for the last non-zero bucket, but it does produce a more compact representation of the payload (which also works with the downstream vendor). If this would be acceptable to the maintainers, I'm happy to code up a PR with this change.
Describe your environment
Running with:
Requirements:
Steps to reproduce
Run
main.py
(below) and capture the dump of the exponential histogram.Source code:
This is run with the following script:
What is the expected behavior?
I expected to see a dump like that generated for the JavaScript SDK in
dump-js.txt.
What is the actual behavior?
The generated exponential histogram in dump-python.txt seems to have the following problems:
dump-js.txt
) trim unnecessary buckets, reducing the size of the payload.Additional context
None.
The text was updated successfully, but these errors were encountered: