Uh oh!
There was an error while loading. Please reload this page.
feat(otel): Export & use spanTimeInputToSeconds for otel span exporter - #12699
Conversation
AbhiPrasad
left a comment
There was a problem hiding this comment.
Can we add a test for this? Seems really weird that this has this behaviour.
onurtemizkan
commented
Jun 28, 2024
Yes, and I just realised that the PR is also incomplete, we need to detect if it's in milliseconds or seconds. In the issue it's in milliseconds. |
mydea
commented
Jul 1, 2024
Can we instead just export |
onurtemizkan
commented
Jul 1, 2024
Oh I wasn't aware of that! Updating the PR. |
d73b071 to
ae4a0f2Comparesize-limit report 📦
|
ae4a0f2 to
9da19ecComparespanTimeInputToSeconds for otel span exporter
mydea
left a comment
There was a problem hiding this comment.
nice! I adjusted the PR name to match what it now does :) Still weird why this is happening, as the types are pretty clear in what should happen, but does not hurt to be extra safe here...
Adds support for cases where the time from OTEL is just a number in milliseconds instead of tuples.
Fixes: #12697 (Can't reproduce the issue but from the context of the report, this should resolve it)