<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Feroda logs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Feroda-logs/m-p/153085#M31157</link>
    <description>&lt;P&gt;Hi templier,&lt;/P&gt;

&lt;P&gt;your biggest trouble here is the binary format of the &lt;CODE&gt;journalctl&lt;/CODE&gt; logs. Quick and dirty solutions would be:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;run a wrapper for &lt;CODE&gt;journalctl -f&lt;/CODE&gt; into a log file and monitor that in Splunk&lt;/LI&gt;
&lt;LI&gt;or read this &lt;A href="https://medium.com/coreos-linux-for-massive-server-deployments/coreos-logging-to-remote-destinations-defb984185c5"&gt;https://medium.com/coreos-linux-for-massive-server-deployments/coreos-logging-to-remote-destinations-defb984185c5&lt;/A&gt; where they use &lt;CODE&gt;ncat&lt;/CODE&gt; to send journalctl output directly into Splunk&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Tue, 17 Feb 2015 12:48:22 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2015-02-17T12:48:22Z</dc:date>
    <item>
      <title>Feroda logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Feroda-logs/m-p/153084#M31156</link>
      <description>&lt;P&gt;Hello. &lt;/P&gt;

&lt;P&gt;Does anyone have experience with what is reflected in the subject question (Journalctl logs)? &lt;BR /&gt;
I must copy the security log with Fedora Journalctl.&lt;/P&gt;

&lt;P&gt;But which side to approach him, I do not know yet&lt;/P&gt;</description>
      <pubDate>Tue, 17 Feb 2015 12:23:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Feroda-logs/m-p/153084#M31156</guid>
      <dc:creator>templier</dc:creator>
      <dc:date>2015-02-17T12:23:19Z</dc:date>
    </item>
    <item>
      <title>Re: Feroda logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Feroda-logs/m-p/153085#M31157</link>
      <description>&lt;P&gt;Hi templier,&lt;/P&gt;

&lt;P&gt;your biggest trouble here is the binary format of the &lt;CODE&gt;journalctl&lt;/CODE&gt; logs. Quick and dirty solutions would be:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;run a wrapper for &lt;CODE&gt;journalctl -f&lt;/CODE&gt; into a log file and monitor that in Splunk&lt;/LI&gt;
&lt;LI&gt;or read this &lt;A href="https://medium.com/coreos-linux-for-massive-server-deployments/coreos-logging-to-remote-destinations-defb984185c5"&gt;https://medium.com/coreos-linux-for-massive-server-deployments/coreos-logging-to-remote-destinations-defb984185c5&lt;/A&gt; where they use &lt;CODE&gt;ncat&lt;/CODE&gt; to send journalctl output directly into Splunk&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Tue, 17 Feb 2015 12:48:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Feroda-logs/m-p/153085#M31157</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-02-17T12:48:22Z</dc:date>
    </item>
    <item>
      <title>Re: Feroda logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Feroda-logs/m-p/153086#M31158</link>
      <description>&lt;P&gt;Hi. &lt;/P&gt;

&lt;P&gt;Yes, both options are not perfect, but it seems if there is no other choice on them have to stop.&lt;BR /&gt;
Now looking information whether it is possible simultaneously to configure logging to files (similar secure.log)&lt;/P&gt;

&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Feb 2015 12:52:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Feroda-logs/m-p/153086#M31158</guid>
      <dc:creator>templier</dc:creator>
      <dc:date>2015-02-17T12:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: Feroda logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Feroda-logs/m-p/153087#M31159</link>
      <description>&lt;P&gt;systemd will send events to syslog. Which should write out to /var/log/..&lt;BR /&gt;
enable in &lt;BR /&gt;
&lt;CODE&gt;/etc/systemd/journald.conf&lt;/CODE&gt;&lt;BR /&gt;
set&lt;BR /&gt;
&lt;CODE&gt;ForwardToSyslog=yes&lt;/CODE&gt;&lt;BR /&gt;
rsyslog appears to have a listener configured (on centos at least) in&lt;BR /&gt;
&lt;CODE&gt;/etc/rsyslog.d/listen.conf&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;$SystemLogSocketName /run/systemd/journal/syslog&lt;/CODE&gt;&lt;BR /&gt;
I guess you will need to restart the service&lt;BR /&gt;
&lt;CODE&gt;systemctl restart systemd-journald&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;see also&lt;BR /&gt;
&lt;A href="https://www.loggly.com/docs/systemd-logs/"&gt;https://www.loggly.com/docs/systemd-logs/&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://forums.opensuse.org/showthread.php/488025-Syslog-and-journalctl"&gt;https://forums.opensuse.org/showthread.php/488025-Syslog-and-journalctl&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://www.freedesktop.org/software/systemd/man/journald.conf.html"&gt;https://www.freedesktop.org/software/systemd/man/journald.conf.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jul 2016 13:26:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Feroda-logs/m-p/153087#M31159</guid>
      <dc:creator>quixand</dc:creator>
      <dc:date>2016-07-29T13:26:49Z</dc:date>
    </item>
  </channel>
</rss>

