<?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 №42</title>
    <link>https://blog.no42.org/tags/telemetry/</link>
    <description>Recent content in Telemetry on №42</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 16 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.no42.org/tags/telemetry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>gNMI dial-in vs. dial-out – Who picks up the phone</title>
      <link>https://blog.no42.org/article/gnmi-dialin-dialout/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.no42.org/article/gnmi-dialin-dialout/</guid>
      <description>&lt;p&gt;I work with people who build network monitoring systems.&#xA;SNMP Traps, NetFlow and IPFIX, BMP — in all of them the device pushes and the collector listens.&#xA;And in all of them the device reaches &lt;em&gt;out&lt;/em&gt;: nothing has to connect &lt;em&gt;into&lt;/em&gt; the fleet.&lt;/p&gt;&#xA;&lt;p&gt;Then you deploy gNMI dial-in and a colleague asks why this one stream connects the other way around.&#xA;Good question, and it took me a while to give a honest answer.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
