<?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 Precomputing.com</title>
    <link>https://precomputing.com/tags/opentelemetry/</link>
    <description>Recent content in Opentelemetry on Precomputing.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://precomputing.com/tags/opentelemetry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Precomputing Now Takes OpenTelemetry and Lets a Running File Change Its Policy</title>
      <link>https://precomputing.com/precomputing-now-takes-opentelemetry-and-lets-a-running-file-change-its-policy/</link>
      <pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://precomputing.com/precomputing-now-takes-opentelemetry-and-lets-a-running-file-change-its-policy/</guid>
      <description>&lt;p&gt;Precomputing 0.3 is out. It closes the four gaps that stood between it and a real deployment. Applications and OpenTelemetry Collectors can send logs and metrics straight to &lt;code&gt;precomputing serve&lt;/code&gt; over OTLP/HTTP. The server speaks HTTPS. A billing stream can refuse a report from a gateway whose clock runs ahead. And a file that has been running for months can take a new version of its policy without starting over.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
