<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Telemetry on gNMIc Operator</title><link>https://fbe70dc2.gnmic-operator2.pages.dev/tags/telemetry/</link><description>Recent content in Telemetry on gNMIc Operator</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 17 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://fbe70dc2.gnmic-operator2.pages.dev/tags/telemetry/index.xml" rel="self" type="application/rss+xml"/><item><title>Designing Telemetry Pipelines</title><link>https://fbe70dc2.gnmic-operator2.pages.dev/blog/2026-03-17-telemetry-pipeline-design/</link><pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate><guid>https://fbe70dc2.gnmic-operator2.pages.dev/blog/2026-03-17-telemetry-pipeline-design/</guid><description>&lt;p>Managing gNMI telemetry at scale is not just a configuration problem. It&amp;rsquo;s an ownership problem. Subscriptions change often. Targets come and go. Different teams care about different slices of the network. And when your collector fleet spans multiple pods serving hundreds of devices, the last thing you want is a design where updating a Kafka output triggers a rolling restart, or where scaling from 3 to 5 pods means touching your telemetry wiring.&lt;/p></description></item><item><title>Introducing gNMIc Operator</title><link>https://fbe70dc2.gnmic-operator2.pages.dev/blog/2026-02-08-introducing-gnmic-operator/</link><pubDate>Sun, 08 Feb 2026 00:00:00 +0000</pubDate><guid>https://fbe70dc2.gnmic-operator2.pages.dev/blog/2026-02-08-introducing-gnmic-operator/</guid><description>&lt;p>Today we&amp;rsquo;re releasing &lt;strong>gNMIc Operator&lt;/strong>: A Kubernetes operator that brings cloud-native lifecycle management to &lt;a href="https://gnmic.openconfig.net/">gNMIc&lt;/a> telemetry collectors. It&amp;rsquo;s been a long road to get here, and I want to share a bit of the backstory.&lt;/p>
&lt;h2 id="an-idea-almost-4-years-in-the-making-todo-list">An idea almost 4 years in the &lt;del>making&lt;/del> TODO list&lt;/h2>
&lt;p>The idea was always clear: gNMIc should not only be a powerful CLI tool, but also a scalable, production-grade telemetry collector that could be orchestrated alongside the rest of your infrastructure. That led to multiple improvements to gNMIc (Clustering, Target Loaders,&amp;hellip;), but one of them was a bit more ambitious than the others: A gNMIc Kubernetes operator.&lt;/p></description></item></channel></rss>