OpenTelemetry non compliant trace ids

I recently worked on a new ecommerce project which was using my favorite OpenTelemetry vendor Honeycomb.io, and the stack running in NodeJS/NextJS on a combination of Azure Containers Apps and Azure Functions. Unfortunately, when inspecting the state of the traces I found the following issues:

• A mix of Sentry tracing/samplers and default OpenTelemetry setup
• Frontend and backend traces are not linked
• Traces are missing parent spans/traces
• None of the Azure Functions are instrumented

Luckily I’ve now done multiple projects where I fixed most of these issues, or know how to solve them (or so I thought).