<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Opentelemetry on BareProxy.com</title>
    <link>https://bareproxy.com/tags/opentelemetry/</link>
    <description>Recent content in Opentelemetry on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/opentelemetry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy OpenTelemetry Export Plugin: Request Records Sent to Your Tracing and Log Stores</title>
      <link>https://bareproxy.com/bareproxy-opentelemetry-export-plugin-request-records-sent-to-your-tracing-and-log-stores/</link>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-opentelemetry-export-plugin-request-records-sent-to-your-tracing-and-log-stores/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Status: planned, number 15 of 21 in BareProxy&amp;rsquo;s build order.&lt;/strong&gt; The plugins are built easiest first, and this one is two or three days of coding: records batched and sent in the OpenTelemetry format. It comes after the Uptime checks and status pages plugin. This post describes what it will do, and it will be updated as it is built.&lt;/p&gt;&#xA;&lt;p&gt;BareProxy already writes one record for every request: what arrived, which rule handled it, which backend answered, how long each step took, and what every plugin did. It also passes on a W3C &lt;code&gt;traceparent&lt;/code&gt; header, so a request&amp;rsquo;s trace in the app joins up with the proxy&amp;rsquo;s request ID. What&amp;rsquo;s missing is a way to get those records into the tools teams already use: Grafana, Honeycomb, Datadog, Jaeger, an Elastic stack, or any OpenTelemetry collector.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
