<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Telemetry - Tag - IT Guy Journals</title>
        <link>https://www.itguyjournals.com/tags/telemetry/</link>
        <description>Telemetry - Tag - IT Guy Journals</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>luka.krapic@gmail.com (Luka Krapić)</managingEditor>
            <webMaster>luka.krapic@gmail.com (Luka Krapić)</webMaster><lastBuildDate>Sun, 20 Jul 2025 13:44:59 &#43;0200</lastBuildDate><atom:link href="https://www.itguyjournals.com/tags/telemetry/" rel="self" type="application/rss+xml" /><item>
    <title>How Telemetry Systems Evolve with Infrastructure: Example Architectures from Startup to Enterprise</title>
    <link>https://www.itguyjournals.com/how-telemetry-systems-evolve-with-infrastructure/</link>
    <pubDate>Sun, 20 Jul 2025 13:44:59 &#43;0200</pubDate>
    <author>Luka Krapić</author>
    <guid>https://www.itguyjournals.com/how-telemetry-systems-evolve-with-infrastructure/</guid>
    <description><![CDATA[<p>In <a href="../introduction-to-telemetry-systems/" rel="">our previous post</a>, we introduced the fundamentals of telemetry—covering logs, metrics, traces, and security monitoring. In this follow-up, we’re shifting from theory to practice: what do telemetry stacks actually look like in real-world environments?</p>
<p>The answer depends heavily on infrastructure. In reality, <strong>infrastructure decisions come first</strong>, and the telemetry stack adapts to support what’s already in place—not the other way around. Observability evolves as a response to growing scale, complexity, and operational maturity.</p>]]></description>
</item>
<item>
    <title>Structured Logging in Python</title>
    <link>https://www.itguyjournals.com/structured-logging-in-python/</link>
    <pubDate>Sat, 21 Jun 2025 17:50:06 &#43;0200</pubDate>
    <author>Luka Krapić</author>
    <guid>https://www.itguyjournals.com/structured-logging-in-python/</guid>
    <description><![CDATA[<p>In modern DevOps workflows, observability plays an important role. Operating distributed systems often depends on telemetry data, including metrics, traces, and logs. Logs are frequently a detailed source of information during troubleshooting. Traditional unstructured log messages, written as free-form text, can make it difficult to extract useful information automatically.</p>
<p>Structured logging organizes log data into a consistent, machine-readable format. For a primer on telemetry systems and observability fundamentals, see the blog post <a href="../introduction-to-telemetry-systems" rel="">Introduction to Telemetry Systems</a>.</p>]]></description>
</item>
<item>
    <title>Introduction to Telemetry Systems: The Backbone of Observability</title>
    <link>https://www.itguyjournals.com/introduction-to-telemetry-systems/</link>
    <pubDate>Sat, 31 May 2025 12:31:42 &#43;0200</pubDate>
    <author>Luka Krapić</author>
    <guid>https://www.itguyjournals.com/introduction-to-telemetry-systems/</guid>
    <description><![CDATA[<p>Modern software systems are complex, distributed, and constantly evolving. Whether you&rsquo;re deploying microservices in Kubernetes or managing legacy systems in the cloud, one truth holds: you need visibility. That’s where telemetry systems come in. They provide the data and structure needed to observe, understand, and operate IT systems with confidence.</p>
<p>In this post, we’ll explore the fundamentals of telemetry systems, how they work, the types of data they handle, and why they’re indispensable for achieving observability.</p>]]></description>
</item>
</channel>
</rss>
