<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Observability on Enzo Nocera (@raskyld) - Personal Blog</title>
    <link>https://raskyld.dev/tags/observability/</link>
    <description>Recent content in Observability on Enzo Nocera (@raskyld) - Personal Blog</description>
    <generator>Hugo -- 0.134.2</generator>
    <language>en</language>
    <lastBuildDate>Tue, 23 May 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://raskyld.dev/tags/observability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A primer on effective monitoring practices</title>
      <link>https://raskyld.dev/posts/primer-monitoring/</link>
      <pubDate>Tue, 23 May 2023 00:00:00 +0000</pubDate>
      <guid>https://raskyld.dev/posts/primer-monitoring/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Originally posted on
&lt;a href=&#34;https://www.scaleway.com/en/blog/effective-monitoring-practices/&#34;&gt;Scaleway&amp;rsquo;s Blog&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;As Platform Engineers specialized in monitoring and observability solutions,
my coworkers and I had the chance to experiment a lot with monitoring practices
and tools. Now we would like to share our views on implementing monitoring in a
way that allows your product to become more resilient and responsive.&lt;/p&gt;
&lt;p&gt;Monitoring has a significant impact on your product and its quality.
In our experience, naive attempts to implement monitoring systems without the
accompanying organizational and cultural shifts that allow teams to compensate
for the high costs of monitoring and guarantee that the system in place is
aligned with their goals always fail.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
