<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Prometheus on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/prometheus/</link><description>Recent content in Prometheus on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 20 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/prometheus/index.xml" rel="self" type="application/rss+xml"/><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>Real-time Insights: Dashboards, Alerting, and Anomaly Detection</title><link>https://ai-blog.noorshomelab.dev/ai-observability-guide/realtime-insights-dashboards-alerting-anomaly-detection/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ai-observability-guide/realtime-insights-dashboards-alerting-anomaly-detection/</guid><description>&lt;h2 id="introduction-from-data-to-actionable-insights"&gt;Introduction: From Data to Actionable Insights&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid AI observability enthusiast! In our previous chapters, we embarked on a fascinating journey, learning how to instrument our AI applications with comprehensive logging, tracing, and metrics collection. We discovered how to capture rich data about prompts, responses, model performance, and even the often-elusive costs associated with running our intelligent systems.&lt;/p&gt;
&lt;p&gt;But collecting data is only half the battle. Imagine having a treasure chest full of gold, but no map to find it or tools to spend it. That&amp;rsquo;s what raw observability data can feel like without the right mechanisms to visualize, interpret, and act upon it. This chapter is all about transforming that raw data into powerful, real-time insights that empower you to understand your AI systems at a glance, anticipate problems before they escalate, and react swiftly to unexpected behaviors.&lt;/p&gt;</description></item><item><title>Monitoring and Observability for Production LLMs</title><link>https://ai-blog.noorshomelab.dev/llmops-ai-infra-guide-2026/monitoring-observability-production-llms/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/llmops-ai-infra-guide-2026/monitoring-observability-production-llms/</guid><description>&lt;h2 id="monitoring-and-observability-for-production-llms"&gt;Monitoring and Observability for Production LLMs&lt;/h2&gt;
&lt;p&gt;Welcome back, fellow MLOps engineers and data scientists! In our previous chapters, we&amp;rsquo;ve explored the exciting world of building robust LLM inference pipelines, optimizing them for GPU usage, implementing smart caching strategies, and designing for scalability. We&amp;rsquo;ve laid a strong foundation, but there&amp;rsquo;s a crucial piece missing: How do we &lt;em&gt;know&lt;/em&gt; if our systems are actually performing as expected in the wild? How do we catch issues before our users do?&lt;/p&gt;</description></item><item><title>Hands-On Project: End-to-End AI Observability Implementation</title><link>https://ai-blog.noorshomelab.dev/ai-observability-guide/hands-on-project-end-to-end-ai-observability-implementation/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ai-observability-guide/hands-on-project-end-to-end-ai-observability-implementation/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to the grand finale of our AI Observability journey! In previous chapters, we&amp;rsquo;ve explored the theoretical foundations of logging, tracing, and metrics for AI systems, understanding &lt;em&gt;what&lt;/em&gt; they are and &lt;em&gt;why&lt;/em&gt; they&amp;rsquo;re crucial. Now, it&amp;rsquo;s time to roll up our sleeves and bring these concepts to life with a hands-on project.&lt;/p&gt;
&lt;p&gt;This chapter will guide you through building a complete, end-to-end observability pipeline for a simple Large Language Model (LLM) application. We&amp;rsquo;ll instrument our Python-based LLM service using OpenTelemetry for distributed tracing, custom metrics, and structured logging. Then, we&amp;rsquo;ll deploy an observability backend (SigNoz, which bundles Prometheus and Grafana) using Docker to collect, store, and visualize all our precious AI operational data. Get ready to see your AI system&amp;rsquo;s inner workings like never before!&lt;/p&gt;</description></item><item><title>Chapter 14: DevOps Best Practices, Monitoring &amp;amp; Troubleshooting</title><link>https://ai-blog.noorshomelab.dev/devops-journey-2026/devops-best-practices-monitoring/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/devops-journey-2026/devops-best-practices-monitoring/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 14! You&amp;rsquo;ve come a long way, building a solid foundation in Linux, version control with Git, mastering CI/CD with GitHub Actions and Jenkins, containerizing applications with Docker, and orchestrating them with Kubernetes. You&amp;rsquo;ve even set up robust web servers with Nginx and Apache. That&amp;rsquo;s a huge achievement!&lt;/p&gt;
&lt;p&gt;However, the journey doesn&amp;rsquo;t end when your application is deployed. In the real world, systems can be complex, and things &lt;em&gt;will&lt;/em&gt; go wrong. This is where DevOps truly shines: not just in building and deploying, but in maintaining, observing, and continuously improving your systems in production. This chapter will equip you with the knowledge and tools to ensure your applications run reliably, efficiently, and securely.&lt;/p&gt;</description></item><item><title>Chapter 16: Monitoring and Debugging Vector Search Systems</title><link>https://ai-blog.noorshomelab.dev/usearch-scylladb-vector-search-guide-2026/16-monitoring-debugging/</link><pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/usearch-scylladb-vector-search-guide-2026/16-monitoring-debugging/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 16! So far, we&amp;rsquo;ve explored the fascinating world of vector search, diving deep into USearch and its powerful integration with ScyllaDB. We&amp;rsquo;ve learned how to store, index, and query high-dimensional vectors, enabling intelligent applications like recommendation engines and semantic search. But what happens when things don&amp;rsquo;t go as planned? How do you ensure your vector search system is performing optimally, and what do you do when it&amp;rsquo;s not?&lt;/p&gt;</description></item></channel></rss>