Menu

Post image 1
Post image 2
Post image 3
1 / 3
0

Embedding Drift Detection: A 50-Line Monitor for Production RAG

DEV Community·Gabriel Anhaia·28 days ago
#kVg2a5GR
#rag#ai#observability#class#corpus#mean
Reading 0:00
15s threshold

Book: RAG Pocket Guide: Retrieval, Chunking, and Reranking Patterns for Production Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools Me: xgabriel.com | GitHub When the embedding API itself collapses, the moments-based detector I wrote about earlier catches it. This post is about the other failure mode: the API is fine, your data has moved, and your dashboard still says green. You ship a product launch on Monday. New SKUs, new docs, three thousand fresh chunks indexed alongside the existing eighty thousand. Nothing in the RAG pipeline changed. The embedding model is pinned. The chunker is pinned. The reranker config is byte-for-byte the same as last week. By Wednesday, the support team is forwarding screenshots. Customers asking about the old product line are getting answers that quote the new one. Top-1 hit rate on your eval set is fine.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More