From e336ca87d528a09d01613ccd951bec1704e94572 Mon Sep 17 00:00:00 2001 From: Alexsander Hamir Date: Sat, 7 Feb 2026 15:15:20 -0800 Subject: [PATCH] docs: add LiteLLM Observatory section to v1.81.9 release notes - Add paragraph on release validation, extensibility, and 100% coverage goal - Include OOMs and CPU regressions as issues surfaced under sustained load --- docs/my-website/release_notes/v1.81.9.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/my-website/release_notes/v1.81.9.md b/docs/my-website/release_notes/v1.81.9.md index 966a5dd5f32..ae05f2ffc1f 100644 --- a/docs/my-website/release_notes/v1.81.9.md +++ b/docs/my-website/release_notes/v1.81.9.md @@ -46,6 +46,13 @@ pip install litellm==1.81.9 - **A2A Agent Gateway** - [Call A2A (Agent-to-Agent) registered agents through the standard `/chat/completions` API](../../docs/a2a_invoking_agents) - **Expose MCP servers on the public internet** - [Launch MCP servers with public/private visibility and IP-based access control for internet-facing deployments](../../docs/mcp_public_internet) - **Performance Optimizations** - Multiple performance improvements including ~40% Prometheus CPU reduction, LRU caching, and optimized logging paths +- **LiteLLM Observatory** - [Automated 24-hour load tests](../../blog/litellm-observatory) + +--- + +## LiteLLM Observatory + +LiteLLM Observatory is a long-running release-validation system we built to catch regressions before they reach users. The system is built to be extensible—you can add new tests, configure models and failure thresholds, and queue runs against any deployment. Our goal is to achieve 100% coverage of LiteLLM functionality through these tests. We run 24-hour load tests against our production deployments before all releases, surfacing issues like resource lifecycle bugs, OOMs, and CPU regressions that only appear under sustained load. ---