From 5de7fe289760b8a12bfe7b8eb8c13eb0ba215fed Mon Sep 17 00:00:00 2001 From: Alexsander Hamir Date: Sat, 7 Feb 2026 15:24:15 -0800 Subject: [PATCH] docs: add LiteLLM Observatory section to v1.81.9 release notes (#20675) - 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 a132e0c54e..ca7bb503fe 100644 --- a/docs/my-website/release_notes/v1.81.9.md +++ b/docs/my-website/release_notes/v1.81.9.md @@ -47,6 +47,13 @@ pip install litellm==1.81.9 - **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) - **UI Team Soft Budget Alerts** - [Set soft budgets on teams and receive email alerts when spending crosses the threshold — without blocking requests](../../docs/proxy/ui_team_soft_budget_alerts) - **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. ---