<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Opentelemetry - vo.rs</title><link>https://vo.rs/tags/opentelemetry/</link><description>Latest from the Opentelemetry desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 09 Jul 2026 06:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/opentelemetry/" rel="self" type="application/rss+xml"/><item><title>OpenTelemetry at Home: Traces, Metrics, Logs</title><link>https://vo.rs/story/opentelemetry-at-home-traces-metrics-logs/</link><description>&lt;p&gt;For years my homelab observability was three unrelated tools that happened to share a Grafana dashboard. Prometheus scraped metrics endpoints. Loki tailed logs. And when a request was slow, I had no idea why, because nothing told me which service in the chain was actually the bottleneck — I&amp;rsquo;d grep logs across four containers by timestamp and hope the clocks agreed. That last part is what traces are for, and it&amp;rsquo;s the piece most homelabs never bother with, because setting up distributed tracing used to mean picking a vendor-specific agent and hoping it played nicely with everything else.&lt;/p&gt;</description><pubDate>Thu, 09 Jul 2026 06:00:00 +0000</pubDate></item></channel></rss>