<?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: Detect/handle parsing error and log format change in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Detect-handle-parsing-error-and-log-format-change/m-p/289405#M55230</link>
    <description>&lt;P&gt;Hi Giuseppe,&lt;/P&gt;

&lt;P&gt;Thank you, we will try this tips.&lt;/P&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
István&lt;/P&gt;</description>
    <pubDate>Fri, 13 Oct 2017 20:24:37 GMT</pubDate>
    <dc:creator>ikulcsar</dc:creator>
    <dc:date>2017-10-13T20:24:37Z</dc:date>
    <item>
      <title>Detect/handle parsing error and log format change</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Detect-handle-parsing-error-and-log-format-change/m-p/289403#M55228</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have been asked about log parsing and parser error detection in Splunk.&lt;/P&gt;

&lt;P&gt;The questions are: In general&lt;BR /&gt;
- how can and should I detect parsing errors in Splunk? (New version of log source, etc without notification to Splunk admin, etc)&lt;BR /&gt;
- how should I handle the new log format? There are already data in the index with the old source type. If I modify the sourcetype definitions, it will break the search time field extraction, is it? Clone and modify the source type?&lt;/P&gt;

&lt;P&gt;I don't find a guide or best practice in the docs...&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
István&lt;/P&gt;</description>
      <pubDate>Fri, 06 Oct 2017 14:30:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Detect-handle-parsing-error-and-log-format-change/m-p/289403#M55228</guid>
      <dc:creator>ikulcsar</dc:creator>
      <dc:date>2017-10-06T14:30:07Z</dc:date>
    </item>
    <item>
      <title>Re: Detect/handle parsing error and log format change</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Detect-handle-parsing-error-and-log-format-change/m-p/289404#M55229</link>
      <description>&lt;P&gt;Hi ikulcsar,&lt;BR /&gt;
to answer to your questions:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;you could detect parsing errors identifing, for each sourcetype) one or more fields with controlling values (e.g.: two or three fields with a limited number of values) that you can store in one or more lookups and periodically (e.g. one time a day) check; in other words you have identify a field, put all the correct values in a  lookup and check if there are more values than the lookup, if there are maybe there's a parsing error to manually check.&lt;/LI&gt;
&lt;LI&gt;to check new sourcetypes, you could use the same method (put all the correct sourcetypes in a lookup an run a search).&lt;/LI&gt;
&lt;LI&gt;to handle the modified sourcetypes you could follow different solutions depending by your situation: 
a. create a new sourcetype for the modified logs and manage the situation using eventtypes (it's a good practice use eventypes in searches),
b. modify extracted fields managing the new and old versions using coalesce funtion; in other words, for each field you maintain the old field extraction, you create a new one and you create a calculated field rule (eval my_field=coalesce(new_field,my_field) to manage the presence of two versions of the same field.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;I hope to be helpful for you.&lt;/P&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 16:12:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Detect-handle-parsing-error-and-log-format-change/m-p/289404#M55229</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-09-29T16:12:23Z</dc:date>
    </item>
    <item>
      <title>Re: Detect/handle parsing error and log format change</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Detect-handle-parsing-error-and-log-format-change/m-p/289405#M55230</link>
      <description>&lt;P&gt;Hi Giuseppe,&lt;/P&gt;

&lt;P&gt;Thank you, we will try this tips.&lt;/P&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
István&lt;/P&gt;</description>
      <pubDate>Fri, 13 Oct 2017 20:24:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Detect-handle-parsing-error-and-log-format-change/m-p/289405#M55230</guid>
      <dc:creator>ikulcsar</dc:creator>
      <dc:date>2017-10-13T20:24:37Z</dc:date>
    </item>
  </channel>
</rss>

