<?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 Faridajalalmd on Medium]]></title>
        <description><![CDATA[Stories by Faridajalalmd on Medium]]></description>
        <link>https://medium.com/@mdfaridajalal?source=rss-699dd4d8eb70------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Faridajalalmd on Medium</title>
            <link>https://medium.com/@mdfaridajalal?source=rss-699dd4d8eb70------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:59:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mdfaridajalal/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[How Dynatrace Dashboards Changed the Way We Look at Reliability]]></title>
            <link>https://medium.com/@mdfaridajalal/how-dynatrace-dashboards-changed-the-way-we-look-at-reliability-8470fd501201?source=rss-699dd4d8eb70------2</link>
            <guid isPermaLink="false">https://medium.com/p/8470fd501201</guid>
            <dc:creator><![CDATA[Faridajalalmd]]></dc:creator>
            <pubDate>Thu, 02 Oct 2025 04:45:11 GMT</pubDate>
            <atom:updated>2025-10-02T04:45:11.647Z</atom:updated>
            <content:encoded><![CDATA[<p>When I started working on observability, dashboards often felt like decoration. There were plenty of graphs and charts, but they didn’t always help the team make faster decisions. The data existed, but it rarely told us what we needed to know in the moment.</p><p>That changed when I helped design and roll out Dynatrace dashboards for a global client. I went in expecting another monitoring setup, but what we created ended up reshaping how the team approached reliability. It wasn’t about adding more information, it was about showing the right context in a way that people could act on immediately.</p><p>One problem I had seen repeatedly was noise. Logs and metrics came in from every corner of the system. CPU usage here, memory there, latency spikes in another tab. During incidents, engineers wasted hours piecing things together instead of fixing the root cause. The information was technically there, but scattered and overwhelming.</p><p>With Dynatrace we built dashboards that cut through that noise. Service health was grouped by business impact instead of raw technical stats. Incidents were correlated so the right people could step in quickly. We pulled key numbers like Mean Time to Resolution into a single view that anyone on the call could understand. It turned troubleshooting from guesswork into a focused process.</p><p>The results spoke for themselves. Mean Time to Resolution dropped by about forty percent. Alert fatigue went down. Engineers trusted the dashboards enough to use them daily, not just during outages. What used to be wallpaper in a monitoring room became the team’s first source of truth.</p><p>That project changed the way I think about reliability. Observability isn’t about collecting endless data points. It’s about giving people the clarity to act in real time. In industries like banking, healthcare, and energy, losing that clarity doesn’t just mean downtime, it means putting critical services at risk.</p><p>Dashboards may look simple from the outside, but when designed with purpose they can be the difference between hours of confusion and minutes to recovery. For me, that was the moment I realized good observability is not just a technical improvement, it’s a cornerstone of resilience at scale.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8470fd501201" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Designed a Dynatrace Dashboard That Made Our Business Users Stop Calling Support]]></title>
            <link>https://medium.com/@mdfaridajalal/how-i-designed-a-dynatrace-dashboard-that-made-our-business-users-stop-calling-support-619aa5433101?source=rss-699dd4d8eb70------2</link>
            <guid isPermaLink="false">https://medium.com/p/619aa5433101</guid>
            <dc:creator><![CDATA[Faridajalalmd]]></dc:creator>
            <pubDate>Wed, 23 Apr 2025 23:24:23 GMT</pubDate>
            <atom:updated>2025-04-23T23:26:22.358Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How I Designed a Dynatrace Dashboard That Made Our Business Users Stop Calling Support</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*loEOIGl-OBCvnMIQPP0PJg.png" /><figcaption>Dev Dashboard Image</figcaption></figure><h3>Intro</h3><p>As engineers, we often design monitoring dashboards for ourselves — but what happens when business teams start using them too? During my time supporting a global energy client, I built a Dynatrace dashboard that became more than just a technical tool. It helped business users understand pipeline health, reduced panic escalations, and actually cut support calls by over 60%.<br> <br> This isn’t a tutorial, it’s a story of how observability, when done right, builds trust across an organization and supports mission-critical operations. And how small engineering choices can have real-world impact.</p><h3>The Problem</h3><p>The client’s core energy trading platform relied on multiple microservices and data pipelines. Operations teams constantly needed to check system health, but they didn’t have access to the tools SREs were using. As a result, every spike in delay or minor error led to Teams pings, Zoom calls, or support tickets.<br> <br> Support fatigue set in, and more importantly, the trust gap between business and tech started growing.</p><h3>My Role</h3><p>I was part of the Site Reliability Engineering team, responsible for observability, uptime, and platform readiness. I proposed building a single Dynatrace dashboard that would serve as a shared visibility hub for both SREs and business stakeholders.<br> <br> The goal was to make something clear, focused, and confidence-building, not just technical charts with 5-second granularity.</p><h3>The Solution</h3><p><strong>Co-designed with business users : </strong>I sat down with operations managers to understand what they actually cared about (e.g., “Are trades flowing?” not “Is Kafka’s memory high?”).</p><p><strong>Created layered visual zones: </strong>Service uptime, trade volume graphs, queue depth, and error summaries were split into visual tiles for quick scanning</p><p><strong>Color-coded health indicators: </strong>Green/yellow/red indicators mapped to thresholds business folks understood. They didn’t need to decode metrics — they needed to know: “Is something wrong?”</p><p><strong>Linked alert context directly into the dashboard: </strong>If an alert fired, clicking it took users straight into a root cause view. That cut time-to-awareness dramatically</p><p><strong>Daily auto-report emails : </strong>I configured Dynatrace to send a dashboard snapshot every morning at 6AM UTC to key team leads. They started checking it before even messaging us.</p><h3>The Outcome</h3><p>— Support ticket volume dropped by over 60% within 3 weeks.<br> — Business users started referring to the dashboard as the “first check” before escalation.<br> — Confidence in system health improved across departments.<br> — We earned back SRE bandwidth and business team trust.<br> <br> And yes — fewer false Sev-1 calls at 2AM</p><h3>Lessons Learned</h3><p><strong>Observability isn’t just for engineers:</strong>If non-technical teams can trust your dashboard, your systems run smoother.</p><p><strong>Designing with empathy builds bridges: </strong>The more you understand what business users *actually* need, the more effective your monitoring becomes</p><p><strong>Simple wins:</strong>Some of the most powerful dashboard features were color tiles and email snapshots — not fancy graphs</p><h3>Closing Note</h3><p>This experience taught me that SRE work doesn’t end with uptime — it extends to communication, transparency, and shared understanding.<br> <br> In high-stakes environments like energy, finance, or healthcare, good observability doesn’t just fix systems. It prevents unnecessary panic, supports critical workflows, and builds infrastructure resilience in a quiet, lasting way.<br> <br> Let me know if you’ve ever tried building a dashboard that had to serve both engineers and business users — I’d love to hear your experience</p><p>#SRE #Dynatrace #Traces #Logs #Metrics #SREPrinciples#Automation#Site Reliability Engineering #Azure #DevOps #Cloud Infrastructure #Observability</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=619aa5433101" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Reduced Alert Fatigue by 30% Using Azure Monitor and Dynatrace]]></title>
            <link>https://medium.com/@mdfaridajalal/how-i-reduced-alert-fatigue-by-30-using-azure-monitor-and-dynatrace-d79e5c730107?source=rss-699dd4d8eb70------2</link>
            <guid isPermaLink="false">https://medium.com/p/d79e5c730107</guid>
            <dc:creator><![CDATA[Faridajalalmd]]></dc:creator>
            <pubDate>Thu, 17 Apr 2025 22:13:56 GMT</pubDate>
            <atom:updated>2025-04-17T23:05:25.331Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Licgp1arG60BSIjb_AY9lw.png" /></figure><h3>Intro</h3><p>In fast-moving production environments, noise can kill signal. During my time supporting a global energy trading platform, I noticed a troubling trend — on-call engineers were drowning in alerts. <strong>Missed alerts. Repeated alerts. False alerts.</strong><br> <br> As a Site Reliability Engineer, I wasn’t just maintaining uptime — I was safeguarding operational continuity for one of the world’s largest energy clients. This post shares how I used Azure Monitor and Dynatrace to cut alert fatigue by 30%, and why this kind of work quietly protects infrastructure that millions rely on every day.</p><h3>The Problem</h3><p>Our alerting strategy had become bloated. Every CPU spike, every transient network error triggered a notification. Over time, critical alerts were buried under a mountain of false positives. Response times dropped. Trust in the system eroded.<br> <br> For a global energy client, this wasn’t just a workflow issue — it threatened the reliability of real-time trade operations, risk evaluations, and compliance tracking across their ETRM systems.</p><h3>My Role &amp; Tools</h3><p>I was part of the SRE team responsible for monitoring, stability, and automation across both on-prem and Azure cloud environments. I led the initiative to re-architect our alerting stack using Azure Monitor and Dynatrace, backed by tight integrations into ServiceNow.<br> <br> My role involved redesigning alert rules, rethinking our telemetry, and building a unified system that prioritized actionability over noise.</p><h3>The Solution</h3><p><strong>Alert Audit</strong> — I cataloged all alerts and classified them into action-required vs. noise. We created a response matrix: what gets escalated, what gets logged, and what gets silenced.<br> <br><strong>Signal-to-Noise Tracking</strong> — I introduced a simple metric: alert-to-incident conversion rate. This became our benchmark for tuning.<br> <br><strong>Dynamic Thresholds in Azure Monitor</strong> — Leveraged smart metrics to reduce unnecessary alerting during known fluctuation windows.<br> <br><strong>Dynatrace Custom Metrics Tuning</strong> — Used custom event processing rules to fine-tune alert granularity. Enabled smarter pattern recognition for composite service failures.<br> <br><strong>Visual Dashboards</strong> — Built shared Grafana-like dashboards through Dynatrace for business and tech teams — transparency reduced the “what’s happening?” queries by 60%.<br> <br><strong>Weekly Feedback Loops</strong>— Integrated support team feedback to fine-tune logic, resulting in greater on-call engineer confidence.</p><h3>The Outcome</h3><p>Alert volume dropped by 30% in six weeks.<br>False Sev-1 incidents were nearly eliminated.<br>Mean Time to Acknowledge improved by 40%.<br>Business teams started self-monitoring with dashboards — freeing up SRE bandwidth.<br> <br> More importantly, system health visibility was restored. Downtime was avoided. And a culture of proactive reliability took root.</p><h3>Lessons Learned</h3><p><strong>Useful alerts are a reliability multiplier-</strong> If engineers trust the system, they act faster and smarter.<br><strong>Observability is everyone’s job- </strong>Dashboards should serve business users, not just backend engineers.<br><strong>Silent systems aren’t healthy systems-</strong> The goal isn’t zero alerts — it’s zero surprises.<br><strong>Resilient infrastructure supports national stability-</strong> Especially in sectors like energy, finance, or healthcare.</p><p>As I continue contributing to infrastructure resilience, I hope this post helps other SREs bring calm to the noise</p><p>Let me know if you’ve faced similar challenges or want to share your own optimization stories</p><p>#Site Reliability Engineering #Azure #DevOps #Cloud Infrastructure #Observability</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d79e5c730107" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Intro]]></title>
            <link>https://medium.com/@mdfaridajalal/quick-intro-a10a25befa2e?source=rss-699dd4d8eb70------2</link>
            <guid isPermaLink="false">https://medium.com/p/a10a25befa2e</guid>
            <dc:creator><![CDATA[Faridajalalmd]]></dc:creator>
            <pubDate>Thu, 17 Apr 2025 21:47:05 GMT</pubDate>
            <atom:updated>2025-10-02T01:27:21.375Z</atom:updated>
            <content:encoded><![CDATA[<p>About Me</p><p>Hi, I’m Faridajalal — a Site Reliability Engineer with over 8 years of experience in cloud automation, observability, and infrastructure reliability across the energy, healthcare, and tech sectors. My work focuses on reducing downtime, scaling systems, and creating operational efficiencies that support critical industries. Through these insights, I aim to share how real-world engineering contributes to national infrastructure resilience and continuity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a10a25befa2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>