News for hackers. Stuff that matters.
Re:The current state of OpenTelemetry by hinkley on Saturday January 13, 2024 @01:22PM (#38982872)
Please, please, to anyone following this thread:

Implement a human readable protocol, then use standardized streaming compression on the wire to get your message size down. Something LZ family because there are tools everywhere that speak them. And consider turning off transport encoding for local development.

Being able to scan data saves so much time on triage. And using zgrep and friends on production data is almost as easy. You will spend tons of effort trying to make something 10% more efficient than zlib or for certain zstd, and the cost is externalized onto your team.

Re:The current state of OpenTelemetry by arccy on Saturday January 13, 2024 @02:48PM (#38983804)
human readable == inefficient parse and processing
Re:The current state of OpenTelemetry by hinkley on Sunday January 14, 2024 @03:03AM (#38988445)
It’s IPC. I think are vastly overestimating the local processing overhead.
Re:The current state of OpenTelemetry by arccy on Sunday January 14, 2024 @08:02AM (#38990039)
there's overhead every time you turn a number from native into a human readable decimal representation, and telemetry is mostly numbers.