<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Syslog on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/syslog/</link>
    <description>Recent content in Syslog on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 02 Nov 2017 12:41:37 +0000</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/syslog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Forward Windows event log entries to syslog server</title>
      <link>https://janikvonrotz.ch/2017/11/02/forward-windows-event-log-entries-to-syslog-server/</link>
      <pubDate>Thu, 02 Nov 2017 12:41:37 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2017/11/02/forward-windows-event-log-entries-to-syslog-server/</guid>
      <description>&lt;p&gt;Syslog is the defacto standard for sending log messages in an IP network. Instead of pulling log messages from a remote computer as you would do it in a windows environment, the log files are sent by remote computers to a central log repository. This way of managing log files has become the standard for Linux / Unix environments. As our IT systems tends to become hybrids, the questions arises how it possible to send syslog messages from a windows computer. In this post I will present you a simple approach.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
