<?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: Why are we missing data in Splunk after rsyslog? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283022#M54100</link>
    <description>&lt;P&gt;We have been using both syslog forwarding as well as TCP listen provided by Splunk for on boarding data from different sources such as firewall which produces large chunk of  data. Yet, we are getting all data on boarded.  &lt;/P&gt;

&lt;P&gt;Can you find out any pattern in data that's missed ? Do you have any log rotation policy?&lt;/P&gt;</description>
    <pubDate>Fri, 29 Jul 2016 05:08:29 GMT</pubDate>
    <dc:creator>hardikJsheth</dc:creator>
    <dc:date>2016-07-29T05:08:29Z</dc:date>
    <item>
      <title>Why are we missing data in Splunk after rsyslog?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283016#M54094</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I am missing data in my current setup (about 20 to 30%).&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Instance A is sending data to Instance B on port 514&lt;/LI&gt;
&lt;LI&gt;Instance B uses rsyslog to get the data and log it into a file called /var/log/app.log&lt;/LI&gt;
&lt;LI&gt;Splunk indexes /var/log/app.log&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;All the data from Intance A is arriving perfectly well into /var/log/app.log.&lt;BR /&gt;
However, some events are missing in Splunk.&lt;/P&gt;

&lt;P&gt;Would you have any idea about the potential issue please? &lt;BR /&gt;
Thank you very much in advance&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2016 00:44:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283016#M54094</guid>
      <dc:creator>Arkon</dc:creator>
      <dc:date>2016-07-28T00:44:23Z</dc:date>
    </item>
    <item>
      <title>Re: Why are we missing data in Splunk after rsyslog?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283017#M54095</link>
      <description>&lt;P&gt;Are you sure it is "missing"?&lt;/P&gt;

&lt;P&gt;We had a multiple problems with time extracion.&lt;BR /&gt;
 - another timstamp in the message, that was pickup as time&lt;BR /&gt;
 - an ID was picked-up as Epoch time&lt;BR /&gt;
 - wrong cut-off for timestamp. (timestamp without year followed by IP address. first 2 digits of the IP where used as YEAR&lt;/P&gt;

&lt;P&gt;To see if the timestamp is wrong, start a real-time search. Just watch the timeline for events popping up in the past.&lt;/P&gt;

&lt;P&gt;If they pop up in the past, you have to alter the props.conf for time extraction&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2016 11:58:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283017#M54095</guid>
      <dc:creator>teunlaan</dc:creator>
      <dc:date>2016-07-28T11:58:24Z</dc:date>
    </item>
    <item>
      <title>Re: Why are we missing data in Splunk after rsyslog?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283018#M54096</link>
      <description>&lt;P&gt;If instance B is Splunk instance, I would suggest that you use tcp input in inputs.conf, no need to route through rsyslog. &lt;BR /&gt;
i.e&lt;BR /&gt;
[tcp://instanceA:514]&lt;/P&gt;

&lt;P&gt;For more information refer TCP section in inputs.conf spec.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2016 12:43:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283018#M54096</guid>
      <dc:creator>hardikJsheth</dc:creator>
      <dc:date>2016-07-28T12:43:55Z</dc:date>
    </item>
    <item>
      <title>Re: Why are we missing data in Splunk after rsyslog?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283019#M54097</link>
      <description>&lt;P&gt;Think he is using UDP 514, than rsyslog is a very good Idea.&lt;BR /&gt;
Otherwise you loose data everytime splunk is restarting&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2016 12:51:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283019#M54097</guid>
      <dc:creator>teunlaan</dc:creator>
      <dc:date>2016-07-28T12:51:50Z</dc:date>
    </item>
    <item>
      <title>Re: Why are we missing data in Splunk after rsyslog?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283020#M54098</link>
      <description>&lt;P&gt;I have to use UDP 514 indeed but all the data is arriving well to the file (plus it's just data from the same VPC no very low risk of losing datagrams). So udp is fine, just Splunk not indexing everything from the file. &lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2016 18:01:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283020#M54098</guid>
      <dc:creator>Arkon</dc:creator>
      <dc:date>2016-07-28T18:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: Why are we missing data in Splunk after rsyslog?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283021#M54099</link>
      <description>&lt;P&gt;I am going to try realtime search right now but when I check if the data is arriving, I do a very general search specifically looking for content in the _raw, no sourcetype or source filter. &lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2016 18:03:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283021#M54099</guid>
      <dc:creator>Arkon</dc:creator>
      <dc:date>2016-07-28T18:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: Why are we missing data in Splunk after rsyslog?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283022#M54100</link>
      <description>&lt;P&gt;We have been using both syslog forwarding as well as TCP listen provided by Splunk for on boarding data from different sources such as firewall which produces large chunk of  data. Yet, we are getting all data on boarded.  &lt;/P&gt;

&lt;P&gt;Can you find out any pattern in data that's missed ? Do you have any log rotation policy?&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jul 2016 05:08:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283022#M54100</guid>
      <dc:creator>hardikJsheth</dc:creator>
      <dc:date>2016-07-29T05:08:29Z</dc:date>
    </item>
    <item>
      <title>Re: Why are we missing data in Splunk after rsyslog?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283023#M54101</link>
      <description>&lt;P&gt;Yes we do have logrotation policy. It looks like that the log rotate is the issue but I am not entirely sure yet. Is it the same on your side? . &lt;BR /&gt;
Apparantly that's the log rotation which breaks everything even if i try putting a higher initCrcLength or crcSalt=.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jul 2016 18:56:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-we-missing-data-in-Splunk-after-rsyslog/m-p/283023#M54101</guid>
      <dc:creator>Arkon</dc:creator>
      <dc:date>2016-07-29T18:56:12Z</dc:date>
    </item>
  </channel>
</rss>

