Add blog post about litellm-observatory

[AlexsanderHamir]

Relevant issues

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test

Changes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Building	Preview, Comment	Feb 7, 2026 2:02am

[greptile-apps]

Greptile Overview

Greptile Summary

• Adds a new Docusaurus blog post introducing “LiteLLM Observatory” and describing a long-running release-validation approach.
• Documents a real-world HTTP client lifecycle regression (v1.81.3) and how the Observatory is intended to catch similar long-lived failures.
• Outlines how tests are triggered via an API, queued/deduplicated, executed in the background against LiteLLM deployments, and reported to Slack.

Confidence Score: 4/5

• This PR is low risk and safe to merge after fixing a markdown rendering issue.
• Single documentation-only change; the only concrete problem found is an unmatched trailing code fence that will break markdown rendering for the post.
• docs/my-website/blog/litellm_observatory/index.md

Important Files Changed

Filename	Overview
docs/my-website/blog/litellm_observatory/index.md	Adds a new blog post describing LiteLLM Observatory; file has a markdown rendering bug due to an unmatched trailing triple-backtick at the end of the document.

Sequence Diagram

sequenceDiagram
  autonumber
  participant User as User/CI
  participant ObsAPI as Observatory API
  participant Queue as Test Queue
  participant Runner as Test Runner
  participant LiteLLM as LiteLLM Deployment
  participant Slack as Slack

  User->>ObsAPI: POST /tests {deployment_url, api_key, test_name, settings}
  ObsAPI->>Queue: Enqueue test if not duplicate
  alt Duplicate running/queued
    Queue-->>ObsAPI: Reject duplicate
    ObsAPI-->>User: 409/4xx Duplicate test
  else Accepted
    Queue-->>ObsAPI: Accepted
    ObsAPI-->>User: 202 Accepted (test_id)
    Queue-->>Runner: Dequeue when capacity available
    loop For test duration
      Runner->>LiteLLM: Send model requests
      LiteLLM-->>Runner: Responses / errors
      Runner->>Runner: Track failure rate & thresholds
    end
    Runner->>Slack: Post results summary
  end

Loading

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Unmatched closing code fence

The post ends with a lone closing triple-backtick (`````), but there’s no corresponding opening fence at the end of the article. This will render the remainder of the page (or previous section) as a code block in many markdown renderers. Remove the trailing fence (or add the missing opening fence if intentional).