opentelemetry-python icon indicating copy to clipboard operation
opentelemetry-python copied to clipboard

Published 20 hours ago • verified publisher icon open-telemetry

Feature/json file http exporter

Open NN--- opened this issue 7 months ago • 5 comments

Addition to #4470 to write the id as hex so they can be exported to files.

NN--- avatar Apr 20 '25 08:04 NN---

CLA Signed

The committers listed above are authorized under a signed CLA.

  • :white_check_mark: login: andrewlwn77 (1cacc8413cd2096df2e8e00fdc662fffe71427ea, 9abf25caa7ab15edbbc31d31232ce680d50bfae1, 48a87c647b3bb0e4a5246bcc2f582559f31520ef)
  • :white_check_mark: login: NN--- / name: NN (a34287f6550fc00f66945691b2448634af4d61a2, 278afd45ad74d6a29a6b00fb36cde068c5323020)

linux-foundation-easycla[bot] avatar Apr 20 '25 08:04 linux-foundation-easycla[bot]

@dimaqq Please pay attention to the original PR so the author can address the comments. This just has a small addition on top of it to make it correctly work according to opentelemetry file spec.

NN--- avatar May 13 '25 05:05 NN---

You may consider using https://pypi.org/project/otlp-test-data/ , a small project I made to generate all conceivable "weird" input.

That includes the JSON flavour of OTLP serialisation, to the best of my understanding.

I could be wrong on some details, PRs are welcome :)

dimaqq avatar May 13 '25 05:05 dimaqq

@dimaqq Do you know whether trace and spans ids in http/json are base64 encoded? In files they are hex encoded , hence the addition.

NN--- avatar May 13 '25 05:05 NN---

@dimaqq Do you know whether trace and spans ids in http/json are base64 encoded? In files they are hex encoded , hence the addition.

Do read https://opentelemetry.io/docs/specs/otlp/#json-protobuf-encoding

I mean I can answer your question off the top of my head, but then you'd miss the other half a dozen gotchas.

dimaqq avatar May 13 '25 06:05 dimaqq