<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Logstash on The blog of Mr Wade</title><link>https://www.mrwade.co.uk/tags/logstash/</link><description>Recent content in Logstash on The blog of Mr Wade</description><generator>Hugo</generator><language>en-GB</language><copyright>Copyright © 2026, Michael Wade; all rights reserved.</copyright><lastBuildDate>Tue, 06 Nov 2012 20:49:11 +0800</lastBuildDate><atom:link href="https://www.mrwade.co.uk/tags/logstash/index.xml" rel="self" type="application/rss+xml"/><item><title>Getting started with logstash</title><link>https://www.mrwade.co.uk/posts/getting-started-with-logstash.aspx/</link><pubDate>Wed, 24 Oct 2012 17:35:00 +0800</pubDate><guid>https://www.mrwade.co.uk/posts/getting-started-with-logstash.aspx/</guid><description>&lt;p&gt;&lt;a href="http://logstash.net/" title="Logstash"&gt;Logstash&lt;/a&gt; is a tool for doing fancy stuff with log files. Its main purpose is to help administrators/IT staff with the monitoring of logs, specifically it can be used to push logs to a central location where the logs are stored and indexed for later searching. A basic logstash setup (like the one I am implementing at work) consists of log shippers (web servers and database servers) and then one server where the logs are stored, indexed and searched (in my case this is a Ubuntu server).&lt;/p&gt;</description></item></channel></rss>