<?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 Possible bug in Monitoring Console (Indexing-&amp;gt;Inputs-Data Quality-&amp;gt;Timestamp Parsing issues) in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Possible-bug-in-Monitoring-Console-Indexing-gt-Inputs-Data/m-p/322544#M60083</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have a logfile that generates exceptions. When there is no exception it just generates event lines with a header and a footer.&lt;BR /&gt;
These events without a timestamp generate timestamp parsing issues as expected. &lt;BR /&gt;
This is shown in the MC--&amp;gt;ndexing-&amp;gt;Inputs-Data Quality-&amp;gt;Timestamp Parsing issues.&lt;/P&gt;

&lt;P&gt;All correct so far....&lt;/P&gt;

&lt;P&gt;So I have created a props and transforms to send these garbage header and footer events to the nullqueue. This works fine.&lt;BR /&gt;
When I now search for this sourcetype the garbage events do no show up anymore. Exactly what I want....&lt;BR /&gt;
But in the Monitoring Console this sourcetype / header footer garbage events still generate timestamp parsing issues.&lt;BR /&gt;
I think this is a bug in Splunk? &lt;/P&gt;</description>
    <pubDate>Mon, 22 Jan 2018 11:47:41 GMT</pubDate>
    <dc:creator>Azeemering</dc:creator>
    <dc:date>2018-01-22T11:47:41Z</dc:date>
    <item>
      <title>Possible bug in Monitoring Console (Indexing-&gt;Inputs-Data Quality-&gt;Timestamp Parsing issues)</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Possible-bug-in-Monitoring-Console-Indexing-gt-Inputs-Data/m-p/322544#M60083</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have a logfile that generates exceptions. When there is no exception it just generates event lines with a header and a footer.&lt;BR /&gt;
These events without a timestamp generate timestamp parsing issues as expected. &lt;BR /&gt;
This is shown in the MC--&amp;gt;ndexing-&amp;gt;Inputs-Data Quality-&amp;gt;Timestamp Parsing issues.&lt;/P&gt;

&lt;P&gt;All correct so far....&lt;/P&gt;

&lt;P&gt;So I have created a props and transforms to send these garbage header and footer events to the nullqueue. This works fine.&lt;BR /&gt;
When I now search for this sourcetype the garbage events do no show up anymore. Exactly what I want....&lt;BR /&gt;
But in the Monitoring Console this sourcetype / header footer garbage events still generate timestamp parsing issues.&lt;BR /&gt;
I think this is a bug in Splunk? &lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2018 11:47:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Possible-bug-in-Monitoring-Console-Indexing-gt-Inputs-Data/m-p/322544#M60083</guid>
      <dc:creator>Azeemering</dc:creator>
      <dc:date>2018-01-22T11:47:41Z</dc:date>
    </item>
  </channel>
</rss>

