<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RAG on SRE &amp; AI Field Notes</title><link>https://sre-ai-blog.pages.dev/en/tags/rag/</link><description>Recent content in RAG on SRE &amp; AI Field Notes</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 26 Jul 2026 01:29:48 +0800</lastBuildDate><atom:link href="https://sre-ai-blog.pages.dev/en/tags/rag/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Enterprise Intelligent Operations Knowledge Base with RAG</title><link>https://sre-ai-blog.pages.dev/en/posts/rag-knowledge-base/</link><pubDate>Wed, 15 Jul 2026 00:00:00 +0000</pubDate><guid>https://sre-ai-blog.pages.dev/en/posts/rag-knowledge-base/</guid><description>&lt;h2 id="1-the-pain-of-operations-knowledge-management"&gt;1. The Pain of Operations Knowledge Management&lt;/h2&gt;
&lt;p&gt;In large organizations, operations knowledge is often scattered across Wikis, Runbooks, Slack records, and incident reports. On-call engineers must navigate multiple systems to locate critical information. RAG technology offers a new approach to solving this problem.&lt;/p&gt;
&lt;h2 id="2-system-architecture"&gt;2. System Architecture&lt;/h2&gt;
&lt;p&gt;We built a complete RAG pipeline based on the LangChain framework: documents are parsed, split, and stored in Chroma vector database; when an engineer asks a question, the system first retrieves the most relevant document fragments, then generates an answer via an LLM.&lt;/p&gt;
&lt;h2 id="3-key-technologies-and-implementation"&gt;3. Key Technologies and Implementation&lt;/h2&gt;
&lt;p&gt;We chose text-embedding-3-small as the embedding model, with a chunk size of 512 tokens and 64 token overlap. The retrieval uses a hybrid strategy: vector similarity + BM25 keyword weighting.&lt;/p&gt;</description></item></channel></rss>