<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Metrics on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/metrics/</link><description>Recent content in Metrics on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/metrics/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Your AI Observability Foundation with OpenTelemetry</title><link>https://ai-blog.noorshomelab.dev/ai-observability-guide/building-ai-observability-foundation-opentelemetry/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ai-observability-guide/building-ai-observability-foundation-opentelemetry/</guid><description>&lt;h2 id="introduction-laying-the-observability-groundwork-with-opentelemetry"&gt;Introduction: Laying the Observability Groundwork with OpenTelemetry&lt;/h2&gt;
&lt;p&gt;Welcome back, future AI observability masters! In the previous chapter (or what you&amp;rsquo;d have learned in it!), we explored the &lt;em&gt;why&lt;/em&gt; of AI observability, understanding its critical role in managing the unique complexities of AI systems in production. Now, it&amp;rsquo;s time to dive into the &lt;em&gt;how&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;This chapter is all about building a solid foundation using &lt;strong&gt;OpenTelemetry (OTel)&lt;/strong&gt;, the open-source, vendor-neutral standard for collecting and managing telemetry data. Think of OpenTelemetry as your universal language for telling the story of your AI application&amp;rsquo;s performance, behavior, and health. Why is this so crucial for AI? Because AI systems often involve multiple components, non-deterministic outputs, and a constant need to understand prompt-to-response dynamics. Without a standardized way to collect and correlate data, debugging a misbehaving LLM or an underperforming recommendation engine can feel like searching for a needle in a haystack&amp;hellip; in the dark!&lt;/p&gt;</description></item><item><title>Chapter 3: Logging Metrics, Parameters, and Configs</title><link>https://ai-blog.noorshomelab.dev/trackio-2026-guide/03-logging-metrics-and-parameters/</link><pubDate>Thu, 01 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/trackio-2026-guide/03-logging-metrics-and-parameters/</guid><description>&lt;h2 id="introduction-to-logging-your-ml-story"&gt;Introduction to Logging Your ML Story&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 3! In the previous chapter, we got Trackio up and running and initialized our first experiment. Now, it&amp;rsquo;s time to make that experiment meaningful by recording what truly matters: your model&amp;rsquo;s performance, the settings you used, and the decisions you made along the way.&lt;/p&gt;
&lt;p&gt;This chapter is all about teaching you the art of logging. You&amp;rsquo;ll learn how to capture crucial information like metrics (how well your model is doing), parameters (the knobs and dials you tweaked), and configurations (the overall setup of your experiment). Think of it as writing a detailed lab report for every single machine learning run, but Trackio does most of the heavy lifting!&lt;/p&gt;</description></item><item><title>Chapter 4: The Pillars of Observability: Logs, Metrics, and Traces</title><link>https://ai-blog.noorshomelab.dev/real-world-software-problem-solving-guide/observability-fundamentals/</link><pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/real-world-software-problem-solving-guide/observability-fundamentals/</guid><description>&lt;h2 id="introduction-seeing-inside-your-software"&gt;Introduction: Seeing Inside Your Software&lt;/h2&gt;
&lt;p&gt;Welcome back, aspiring problem-solver! In the previous chapters, we laid the groundwork for a systematic approach to tackling engineering challenges. We learned how to break down complex problems, form hypotheses, and think critically about system behavior. But how do you &lt;em&gt;know&lt;/em&gt; what your system is doing when it&amp;rsquo;s running in production? How do you gather the evidence needed to validate those hypotheses?&lt;/p&gt;
&lt;p&gt;This is where &lt;strong&gt;observability&lt;/strong&gt; comes in. Observability is the ability to infer the internal state of a system by examining its external outputs. It&amp;rsquo;s like having X-ray vision for your software, allowing you to understand &lt;em&gt;why&lt;/em&gt; things are happening, not just &lt;em&gt;that&lt;/em&gt; they are happening. Without good observability, even the most brilliant problem-solving mind is flying blind.&lt;/p&gt;</description></item><item><title>Key Performance Indicators: Metrics for AI Models and Systems</title><link>https://ai-blog.noorshomelab.dev/ai-observability-guide/key-performance-indicators-metrics-ai-models-systems/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ai-observability-guide/key-performance-indicators-metrics-ai-models-systems/</guid><description>&lt;h2 id="introduction-the-pulse-of-your-ai-system"&gt;Introduction: The Pulse of Your AI System&lt;/h2&gt;
&lt;p&gt;Welcome back, fellow AI adventurer! In previous chapters, we laid the groundwork for AI observability by exploring the crucial roles of structured logging and distributed tracing. We learned how to capture &lt;em&gt;events&lt;/em&gt; and &lt;em&gt;flow&lt;/em&gt; within our AI applications. But what about understanding the &lt;em&gt;health&lt;/em&gt; and &lt;em&gt;performance&lt;/em&gt; at a glance? How do we know if our models are performing well, if users are happy, or if costs are spiraling out of control?&lt;/p&gt;</description></item><item><title>Chapter 5: Debugging Production Incidents: A Step-by-Step Guide</title><link>https://ai-blog.noorshomelab.dev/real-world-software-problem-solving-guide/debugging-production-incidents/</link><pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/real-world-software-problem-solving-guide/debugging-production-incidents/</guid><description>&lt;h2 id="chapter-5-debugging-production-incidents-a-step-by-step-guide"&gt;Chapter 5: Debugging Production Incidents: A Step-by-Step Guide&lt;/h2&gt;
&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;Welcome to Chapter 5! In the previous chapters, we laid the groundwork for problem-solving by exploring mental models and systems thinking. Now, we&amp;rsquo;re going to tackle one of the most critical and often stressful aspects of a software engineer&amp;rsquo;s job: debugging production incidents. When systems fail in the real world, the stakes are high. Customers are affected, revenue might be lost, and trust can erode.&lt;/p&gt;</description></item><item><title>Observability: Logging, Metrics, and Distributed Tracing</title><link>https://ai-blog.noorshomelab.dev/systems-engineering-2026/observability-logging-metrics-tracing/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/systems-engineering-2026/observability-logging-metrics-tracing/</guid><description>&lt;p&gt;Imagine your beautifully crafted distributed system running in production. It&amp;rsquo;s composed of many microservices, perhaps handling millions of requests per day, or coordinating a fleet of AI agents. Suddenly, a customer reports an error, or a critical business process slows to a crawl. How do you find out what&amp;rsquo;s going on? Where do you even begin looking?&lt;/p&gt;
&lt;p&gt;This is where &lt;strong&gt;observability&lt;/strong&gt; comes in. It&amp;rsquo;s the ability to infer the internal state of a system by examining its external outputs. In complex, distributed systems, you can&amp;rsquo;t just attach a debugger to a single process. You need to gather data from every corner of your architecture to piece together the full story. This chapter will equip you with the fundamental tools and mindset for achieving deep visibility into your systems: logging, metrics, and distributed tracing.&lt;/p&gt;</description></item><item><title>Chapter 20: Monitoring, Alerting &amp;amp; Maintenance Strategies</title><link>https://ai-blog.noorshomelab.dev/java-mini-projects/ch20-monitoring-maintenance/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/java-mini-projects/ch20-monitoring-maintenance/</guid><description>&lt;h2 id="chapter-20-monitoring-alerting--maintenance-strategies"&gt;Chapter 20: Monitoring, Alerting &amp;amp; Maintenance Strategies&lt;/h2&gt;
&lt;p&gt;Welcome to the final chapter of our comprehensive Java project guide! Throughout this series, we&amp;rsquo;ve focused on building robust, production-ready applications, emphasizing best practices, testing, and deployment. In this concluding chapter, we&amp;rsquo;ll address the critical aspects of operating and maintaining your applications in a real-world environment: monitoring, alerting, and proactive maintenance strategies.&lt;/p&gt;
&lt;p&gt;While our example applications (Calculator, Number Guessing Game, etc.) are relatively simple, the principles of observability and maintainability apply universally. A production-grade application, regardless of its complexity, must provide insights into its health, performance, and behavior. This chapter will guide you through integrating enhanced logging, understanding application metrics, implementing health checks, and establishing a maintenance routine to ensure your Java applications run reliably and efficiently over time.&lt;/p&gt;</description></item><item><title>AI Observability: A Comprehensive Guide</title><link>https://ai-blog.noorshomelab.dev/ai-observability-guide/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ai-observability-guide/</guid><description>&lt;p&gt;Welcome to this essential guide on AI Observability. Here, you will learn how to implement comprehensive monitoring for your AI systems, covering critical aspects like logging, tracing, metrics, and cost management. Discover best practices for tracking prompts, responses, latency, and overall performance to ensure your AI models operate reliably in production environments.&lt;/p&gt;</description></item><item><title>AI Observability: A Practical Guide to Monitoring AI Systems</title><link>https://ai-blog.noorshomelab.dev/guides/ai-observability-guide/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/guides/ai-observability-guide/</guid><description>&lt;p&gt;Welcome to this guide on AI Observability. If you&amp;rsquo;re working with AI models, especially in production, you know that getting them to work is one thing, but making sure they &lt;em&gt;keep&lt;/em&gt; working reliably, efficiently, and cost-effectively is a different challenge. That&amp;rsquo;s exactly what AI observability helps us achieve.&lt;/p&gt;
&lt;h3 id="what-is-ai-observability"&gt;What is AI Observability?&lt;/h3&gt;
&lt;p&gt;In plain language, AI observability is about understanding the internal state of your AI systems—like large language models (LLMs) or custom machine learning models—from their external outputs. It&amp;rsquo;s like giving your AI system a set of senses so you can see, hear, and feel what it&amp;rsquo;s doing, how it&amp;rsquo;s performing, and why it might be behaving in a certain way.&lt;/p&gt;</description></item><item><title>Chapter 6: Performance Investigation: Identifying Bottlenecks</title><link>https://ai-blog.noorshomelab.dev/real-world-software-problem-solving-guide/performance-bottlenecks/</link><pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/real-world-software-problem-solving-guide/performance-bottlenecks/</guid><description>&lt;h2 id="chapter-6-performance-investigation-identifying-bottlenecks"&gt;Chapter 6: Performance Investigation: Identifying Bottlenecks&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid engineer! In the previous chapters, we honed our skills in debugging and understanding system behavior. Now, we&amp;rsquo;re going to tackle one of the most critical and often elusive challenges in software engineering: &lt;strong&gt;performance&lt;/strong&gt;. Ever wondered why a website loads slowly, an API takes ages to respond, or a batch job grinds to a halt? The culprit is usually a &lt;strong&gt;bottleneck&lt;/strong&gt;, and in this chapter, we&amp;rsquo;ll equip you with the mental models and practical tools to find them.&lt;/p&gt;</description></item></channel></rss>