<?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 Chuma Kabaghe on Medium]]></title>
        <description><![CDATA[Stories by Chuma Kabaghe on Medium]]></description>
        <link>https://medium.com/@chumakabaghe?source=rss-975f480c1b04------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*orhRhIZrFXvOXLwv7GRLIQ.jpeg</url>
            <title>Stories by Chuma Kabaghe on Medium</title>
            <link>https://medium.com/@chumakabaghe?source=rss-975f480c1b04------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:56:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chumakabaghe/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[What makes a good web service alert?]]></title>
            <link>https://medium.com/@chumakabaghe/what-makes-a-good-web-service-alert-d94404041d7c?source=rss-975f480c1b04------2</link>
            <guid isPermaLink="false">https://medium.com/p/d94404041d7c</guid>
            <dc:creator><![CDATA[Chuma Kabaghe]]></dc:creator>
            <pubDate>Wed, 04 Sep 2019 17:13:46 GMT</pubDate>
            <atom:updated>2019-09-04T17:15:56.913Z</atom:updated>
            <content:encoded><![CDATA[<p>Alerts play a key role in keeping a web service up and running and most engineers I know value sleep a whole lot. So, if your alert is going to wake them up in the middle of the night, something better be really broken. Here are some guidelines for creating good, useful alerts for your web service.</p><h3>Alerts should:</h3><ol><li>not be noisy, otherwise they get ignored. Fine tune alert thresholds and intervals to ensure every alert sent is relevant.</li><li>require immediate action. Don’t send an alert if the problem is not actionable or urgent. For example, “X Cert expires in 30 days” should be sent as email reminder and “X job ran longer than Y hours” is a notification, not an alert.</li><li>be high priority! Only alert on important things. Everything else can be sent in a daily or weekly report. Failures that impact customers or could lead to data loss are great examples of high priority failures to alert on.</li><li>be self-sufficient. The alert should contain information about what component is failing and in what way it is failing so that appropriate action can be taken immediately.</li><li>contain troubleshooting instructions. The person responding to the alert is not necessarily the one who built the service, so give them some pointers on where to start.</li><li>work. Test your alerts to make sure they work. There’s nothing quite like a system going down and no one knowing about it because someone forgot to turn on the alerts when the service launched.</li><li>be tracked. There should be a way of knowing the status of an alert, who is working on fixing it, and when a fix should be expected.</li><li>be routed to the correct people. Alerting the wrong person leads to time waste as the receiver tries to establish the correct recipient or worse, completely ignores the alert.</li></ol><p>I follow these guidelines every time I create or work on a web service and they have served me and my teammates well so far. I hope you find them useful!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d94404041d7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>