<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ELK on </title>
    <link>https://stoeps.de/tags/elk/</link>
    <description>Recent content in ELK on </description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>christoph.stoettner@stoeps.de (Christoph Stoettner)</managingEditor>
    <webMaster>christoph.stoettner@stoeps.de (Christoph Stoettner)</webMaster>
    <copyright>© 2026 Christoph Stoettner</copyright>
    <lastBuildDate>Thu, 01 Jun 2017 10:15:50 +0000</lastBuildDate><atom:link href="https://stoeps.de/tags/elk/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Orient Me, Elasticsearch and Disk space</title>
      <link>https://stoeps.de/posts/2017/2017-06-01-orient-me-elasticsearch-and-disk-space/</link>
      <pubDate>Thu, 01 Jun 2017 10:15:50 +0000</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2017/2017-06-01-orient-me-elasticsearch-and-disk-space/</guid>
      <description>&lt;p&gt;With &lt;a href=&#34;http://www-03.ibm.com/software/products/en/conn&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;IBM Connections 6&lt;/a&gt;&#xA;you can deploy the&#xA;&lt;a href=&#34;https://www.ibm.com/blogs/ibm-social-software/2017/03/28/ibm-connections-6-0-officially-announced/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;additional&#xA;component Orient Me&lt;/a&gt;, which provides the first microservices which will&#xA;build the new IBM Connections pink. Orient Me is installed on top of&#xA;&lt;a href=&#34;https://www.ibm.com/developerworks/community/groups/service/html/communityoverview?communityUuid=fe25b4ef-ea6a-4d86-a629-6f87ccf4649e&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;IBM&#xA;Spectrum Conductor for Containers&lt;/a&gt; (CFC) a new product to help with&#xA;clustering and orchestrating of the Docker containers.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Better logstash filter to analyze SystemOut.log and some more</title>
      <link>https://stoeps.de/posts/2016/2016-05-29-better-logstash-filter-to-analyze-systemout-log-and-some-more/</link>
      <pubDate>Sun, 29 May 2016 21:11:11 +0000</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2016/2016-05-29-better-logstash-filter-to-analyze-systemout-log-and-some-more/</guid>
      <description>&lt;p&gt;Last week I wrote a post about&#xA;&lt;a href=&#34;https://www.stoeps.de/using-docker-to-analyze-websphere-application-server-systemout-log/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Using Docker and ELK to Analyze WebSphere Application Server SystemOut.log&lt;/a&gt;,&#xA;but i wasn’t happy with my date filter and how the websphere response&#xA;code is analyzed. The main problem was, that the WAS response code is&#xA;not always on the beginning of a log message, or do not end with “:” all&#xA;the time.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Using Docker and ELK to Analyze WebSphere Application Server SystemOut.log</title>
      <link>https://stoeps.de/posts/2016/2016-05-28-using-docker-to-analyze-websphere-application-server-systemout-log/</link>
      <pubDate>Sat, 28 May 2016 14:58:46 +0000</pubDate>
      <author>christoph.stoettner@stoeps.de (Christoph Stoettner)</author>
      <guid>https://stoeps.de/posts/2016/2016-05-28-using-docker-to-analyze-websphere-application-server-systemout-log/</guid>
      <description>&lt;p&gt;I often get SystemOut.log files from customers or friends to help them&#xA;analyzing a problem. Often it is complicated to find the right server&#xA;and application which generates the real error, because most WebSphere&#xA;Applications (like IBM Connections or Sametime) are installed on&#xA;different Application Servers and Nodes. So you need to open multiple&#xA;large files in your editor, scroll each to the needed timestamps and&#xA;check the lines before for possible error messages.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
