<?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: Input gzipped csv files in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Input-gzipped-csv-files/m-p/343737#M63284</link>
    <description>&lt;P&gt;For sourcetype "db2:logs" is there any configuration required.., Should we have to mention anything for index extraction&lt;/P&gt;</description>
    <pubDate>Wed, 10 Apr 2019 09:07:35 GMT</pubDate>
    <dc:creator>hethaishibk</dc:creator>
    <dc:date>2019-04-10T09:07:35Z</dc:date>
    <item>
      <title>Input gzipped csv files</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Input-gzipped-csv-files/m-p/343735#M63282</link>
      <description>&lt;P&gt;Hey Guys,&lt;/P&gt;

&lt;P&gt;I found a few answers regarding my question but I'm still not sure how to handle this situation.&lt;BR /&gt;
I want to index compressed csv files which are in a *.gz format right now.&lt;/P&gt;

&lt;P&gt;My inputs.conf for the forwarder looks like this:&lt;/P&gt;

&lt;P&gt;[monitor:///opt/db2/*.gz]&lt;BR /&gt;
sourcetype = db2:logs&lt;BR /&gt;
index = db2&lt;BR /&gt;
followTail = 0&lt;/P&gt;

&lt;P&gt;Following the documentation here &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitorfilesanddirectories#How_Splunk_Enterprise_monitors_archived_files" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitorfilesanddirectories#How_Splunk_Enterprise_monitors_archived_files&lt;/A&gt; Splunk is able to index compressed files and is decompressing them while indexing. Do I understand this correctly that in this case no more configuration is needed?&lt;/P&gt;

&lt;P&gt;The invalid_cause, unarchive_cmd and unarchive_sourcetype options in the props.conf are making me unsure about that.&lt;BR /&gt;
If i still have to use them, do they need to be on the indexer or aswell in the forwarder app?&lt;/P&gt;

&lt;P&gt;Thanks for getting things straight.&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 13:09:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Input-gzipped-csv-files/m-p/343735#M63282</guid>
      <dc:creator>hypePG</dc:creator>
      <dc:date>2020-09-29T13:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: Input gzipped csv files</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Input-gzipped-csv-files/m-p/343736#M63283</link>
      <description>&lt;P&gt;Ditch the &lt;CODE&gt;followTail&lt;/CODE&gt; setting and you are good-to-go.  You do not need to configure the unarchiving for &lt;CODE&gt;*.gz&lt;/CODE&gt; files; Splunk knows what to do for those.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2017 15:37:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Input-gzipped-csv-files/m-p/343736#M63283</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-03-09T15:37:13Z</dc:date>
    </item>
    <item>
      <title>Re: Input gzipped csv files</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Input-gzipped-csv-files/m-p/343737#M63284</link>
      <description>&lt;P&gt;For sourcetype "db2:logs" is there any configuration required.., Should we have to mention anything for index extraction&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2019 09:07:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Input-gzipped-csv-files/m-p/343737#M63284</guid>
      <dc:creator>hethaishibk</dc:creator>
      <dc:date>2019-04-10T09:07:35Z</dc:date>
    </item>
  </channel>
</rss>

