<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>honeycomb refinery on Freelance senior software consultant</title>
    <link>https://davidweterings.nl/tags/honeycomb-refinery/</link>
    <description>Recent content in honeycomb refinery on Freelance senior software consultant</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 04 Jun 2026 13:30:00 +0200</lastBuildDate><atom:link href="https://davidweterings.nl/tags/honeycomb-refinery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenTelemetry non compliant trace ids</title>
      <link>https://davidweterings.nl/til/honeycomb-bug/</link>
      <pubDate>Thu, 04 Jun 2026 13:30:00 +0200</pubDate>
      
      <guid>https://davidweterings.nl/til/honeycomb-bug/</guid>
      <description>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&amp;rsquo;ve now done multiple projects where I fixed most of these issues, or know how to solve them (or so I thought).</description>
    </item>
    
  </channel>
</rss>
