<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Model Monitoring on ModAPI AI Gateway Knowledge Base</title><link>https://modapi.ai/blog/tags/model-monitoring/</link><description>Recent content in Model Monitoring on ModAPI AI Gateway Knowledge Base</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © ModAPI.ai</copyright><lastBuildDate>Thu, 14 May 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://modapi.ai/blog/tags/model-monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Gateway Observability: Logs, Metrics, and Audit Trails</title><link>https://modapi.ai/blog/observability-for-ai-gateway/</link><pubDate>Thu, 14 May 2026 10:00:00 +0000</pubDate><guid>https://modapi.ai/blog/observability-for-ai-gateway/</guid><description>&lt;p&gt;After a team connects to multiple AI models, the most common production questions are not only &amp;ldquo;Did the request work?&amp;rdquo; They are usually more specific:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Why did this request become slower today?&lt;/li&gt;
&lt;li&gt;Why did this tenant&amp;rsquo;s cost spike?&lt;/li&gt;
&lt;li&gt;Which model actually served this response?&lt;/li&gt;
&lt;li&gt;Did the request use a fallback path?&lt;/li&gt;
&lt;li&gt;Can we explain this model decision later?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Those questions all point to the same requirement: an AI gateway needs observability designed for model calls, not just generic HTTP traffic.&lt;/p&gt;</description></item></channel></rss>