love-hate and otel: using it while avoiding complexity
2 points by StevenAndrewCoffman
2 points by StevenAndrewCoffman
I quite appreciated his workflow for keeping OTel’s complexity at arm’s length. Also, he’s got a generic tool that can parse logs and turn them into otel spans that combines well will canonical logs and “wide events”: https://github.com/jonjohnsonjr/logspan
I wrote https://github.com/wolverian/obs a few days ago exactly because otel is so complicated to set up. It’s a single function that gets you up and running with the SDK, but you’ll still need to instrument your code and run a receiver yourself.
It uses the new-ish auto* packages from otel go contrib. My hope is that at in a few years you won’t even need this function anymore.