<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sebastian Perna on Medium]]></title>
        <description><![CDATA[Stories by Sebastian Perna on Medium]]></description>
        <link>https://medium.com/@sebastianperna?source=rss-27eabe9794c1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*PmtHJpyB3BrxLyRg.</url>
            <title>Stories by Sebastian Perna on Medium</title>
            <link>https://medium.com/@sebastianperna?source=rss-27eabe9794c1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:25:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sebastianperna/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Observability, and the quest to explain it to other people]]></title>
            <link>https://medium.com/@sebastianperna/observability-and-the-quest-to-explain-it-to-other-people-a46f83b8ce2e?source=rss-27eabe9794c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a46f83b8ce2e</guid>
            <category><![CDATA[aiops]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[sre]]></category>
            <category><![CDATA[monitoring]]></category>
            <dc:creator><![CDATA[Sebastian Perna]]></dc:creator>
            <pubDate>Tue, 19 Dec 2023 21:48:10 GMT</pubDate>
            <atom:updated>2023-12-19T21:48:10.521Z</atom:updated>
            <content:encoded><![CDATA[<h4>Did you ever try to explain what observability is?</h4><p>Through the last few years, I have found myself trying to explain to IT teams what observability is and why it is so important for digital solutions. Observability is a popular term among IT people, but despite being a fashion term, not everyone knows what it means or what they should get from it.</p><p>So, in the quest to find a way to define it, I obviously started searching on Google. At first glance, I got multiple definitions and interpretations of what observability means, and all of them seemed to be right, but which one should I use?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*26T342gKwFW8SEjf" /></figure><p>To have so many definitions causes confusion in the community and leads to different expectations when discussing or deploying observability. This, in my opinion, is caused by two factors:</p><p>1) Lack of an Exact Definition:</p><p>Observability was not crafted by a specific group of individuals or a central entity that defines it. Therefore, there is no global and formal definition, leaving its interpretation open to each one. As a result, there are several definitions with diverse approaches. Some people describes it from a technical point of view, others from a business standpoint, as well as others do it with an operational perspective.</p><p>· The technical perspective emphasizes on the data sources that allow us to get information about a system, often referred to as the three pillars of observability: metrics, traces, and logs. These refer to the types of data that can be collected for analysis.</p><p>· The commercial perspective focuses on the products that are on the market that allow us to get the data that we need for observability, as well as the tools that help improve the analysis process.</p><p>· The operational perspective is about the processes and techniques that allow us to analyze data sources that help us understand the state and context of a system at any given moment. It is also defined as being able to ask questions about our systems.</p><p>Each perspective is right but not complete when viewed separately. Taking into account the different definitions that exist, I have created my own version with the aim of simplifying and generalizing those three approaches:</p><blockquote><em>“Observability is the set of tools, data sets, and processes that allow us to analyze and understand the state and context of a system.”</em></blockquote><p>2) Close Relationship with the Term “Monitoring”:</p><p>What about the term “monitoring”? Is there a line of separation between monitoring and observability? If monitoring is also about observing the state of a system, what differentiates them?</p><p>For this there is no clear answer, but yet some interesting interpretations:</p><p>· Observability offers more granular information and context, while monitoring only seeks to warn when a system is not operational.</p><p>· Monitoring seeks fault detection, whereas observability allows for fault prevention. In another words: Observability is proactive, and monitoring is reactive.</p><p>· Monitoring requires predicting the failures that will occur in our system, while observability, by providing more data, allows us to find answers to questions we haven’t even asked yet.</p><p>· Observability adopts multiple data sets as sources, such as logs and traces.</p><p>· With observability, developers have started to take measures to make their systems observable.</p><p>Each one has taken its own definition to set a line of separation between the two concepts. At the same time, companies that develop solutions for this area of work have largely stopped using the term “monitoring” and have almost completely adopted observability. This situation led to the term “monitoring” being forgotten (or replaced) in the market. For some, a new buzzword also presents a strategic opportunity for marketing, providing a rejuvenating touch to legacy monitoring products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*L68Ii0PAXObVDBbvyDaLIQ.png" /></figure><p>In conclusion, this leads me to expand the definition of observability:</p><blockquote><em>“Observability is the evolution of monitoring, with a more proactive perspective on anticipating failures and giving answers about the state of our systems through a large volume of data.”</em></blockquote><h4>Does the exact definition matter?</h4><p>The term defines the how, the philosophy, and the ideal, but ultimately, regardless of the term we use, we always seek the same result: to be advised when something is going wrong in our systems and to have accurate information in order to solve or prevent incidents. Therefore, by getting all of that, we can contribute to providing a good customer experience.</p><p>Observability helps in that common objective by providing the ways to get proactive alerts and enough data for getting answers about our systems at the moment of the resolution of an incident.</p><p>We may broaden the meaning of observability by considering the outcomes:</p><blockquote><em>“We use observability to create proactive alerts for incidents occurring (or about to occur) in our systems and having information to quickly resolve those incidents.</em></blockquote><blockquote><em>Observability adds value to organizations offering digital services by strengthening systems, incident support processes, and ultimately, the customer experience.”</em></blockquote><h4>Conclusion</h4><p>So in the end, I created my own definition of observability. Hope it is useful for you too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7TgTDe_yB-G0AuDaXSJjDg.png" /></figure><blockquote><strong><em>“Observability is a practice that involves using a set of tools, data sets, and processes to analyze and understand the state and context of a system. By using it we can create proactive alerts for incidents occurring (or about to occur) in our systems and have information to quickly resolve those incidents.</em></strong></blockquote><blockquote><strong><em>As a process, observability is the evolution of monitoring, with a more proactive perspective on anticipating failures and giving answers about the state of our systems through a large volume of data.</em></strong></blockquote><blockquote><strong><em>In conclusion, observability adds value to organizations offering digital services by strengthening systems, incident support processes, and ultimately, the customer experience.”</em></strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a46f83b8ce2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>