<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Elasticsearch on Margrop Blog</title>
		<link>https://blog.margrop.net/en/tag/elasticsearch/</link>
		<description>Recent content in Elasticsearch on Margrop Blog</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sat, 11 Jul 2026 03:30:00 +0800</lastBuildDate>
		
			<atom:link href="https://blog.margrop.net/en/tag/elasticsearch/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Stop Reading Logs by Hand: A Practical ELK-to-AI-Agent Guide from Deployment to Assisted Troubleshooting</title>
				<link>https://blog.margrop.net/en/post/elk-ai-agent-hands-on/</link>
				<pubDate>Sat, 11 Jul 2026 03:30:00 +0800</pubDate>
				<guid>https://blog.margrop.net/en/post/elk-ai-agent-hands-on/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://blog.margrop.net/post-images/elk-ai-agent-hands-on/00-cover-ai-generated.png&#34; alt=&#34;ELK connected to an AI Agent&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;The traditional incident-response ritual is familiar: open Kibana, choose a time range, write a query, scan pages of logs, copy a few stack traces, and manually assemble a theory. Once several services are involved, the job feels like finding one screw in a warehouse with no clerk.&lt;/p&gt;&#xA;&lt;p&gt;A better design keeps ELK responsible for dependable ingestion, normalization, search, and visualization, then adds an MCP bridge that lets an AI Agent retrieve evidence through tools. Instead of pasting a giant log file into a chat window, you can ask:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
