<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: bereket teshome</title>
    <description>The latest articles on DEV Community by bereket teshome (@buckygetnet).</description>
    <link>https://dev.to/buckygetnet</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4010187%2F58ed6f59-30da-4196-a78c-973949fbc55f.png</url>
      <title>DEV Community: bereket teshome</title>
      <link>https://dev.to/buckygetnet</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/buckygetnet"/>
    <language>en</language>
    <item>
      <title>The P50 and P99 rule</title>
      <dc:creator>bereket teshome</dc:creator>
      <pubDate>Wed, 01 Jul 2026 02:32:00 +0000</pubDate>
      <link>https://dev.to/buckygetnet/the-p50-and-p99-rule-4o7h</link>
      <guid>https://dev.to/buckygetnet/the-p50-and-p99-rule-4o7h</guid>
      <description>&lt;p&gt;When implementing observability, the metrics you focus on depend heavily on your business requirements. While P50 is usually a good starting point for measuring baseline latency, certain scenarios demand a focus on P99 metrics. Many companies ignore P99 latency, dismissing it as too niche or expensive to justify fixing. However, the 1% of users affected by those delays could easily be your highest-revenue customers.&lt;/p&gt;

&lt;p&gt;This is because the clients falling into that 99th percentile are typically power users who heavily utilize your system, making them the most likely to trigger these edge-case performance bottlenecks.&lt;/p&gt;

</description>
      <category>monitoring</category>
      <category>performance</category>
      <category>sre</category>
    </item>
  </channel>
</rss>
