<?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: Does a CSV import connector or a XML import connector exist in current Splunk versions? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Does-a-CSV-import-connector-or-a-XML-import-connector-exist-in/m-p/609497#M105673</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/248560"&gt;@lwedekind&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;there isn't a predefined connector, because Splunk doesn't use connectors.&lt;/P&gt;&lt;P&gt;But when you have to ingest a csv or a xml file, you have to configure in props.conf an option, called "INDEXED_EXTRACTIONS" and in this way the format is recognized.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;INDEXED_EXTRACTIONS = &amp;lt;CSV|TSV|PSV|W3C|JSON|HEC&amp;gt;
* The type of file that Splunk software should expect for a given source
  type, and the extraction and/or parsing method that should be used on the 
  file.
* The following values are valid for 'INDEXED_EXTRACTIONS':
  CSV  - Comma separated value format
  TSV  - Tab-separated value format
  PSV  - pipe ("|")-separated value format
  W3C  - World Wide Web Consortium (W3C) Extended Log File Format
  JSON - JavaScript Object Notation format
  HEC  - Interpret file as a stream of JSON events in the same format as the 
         HTTP Event Collector (HEC) input.
* These settings change the defaults for other settings in this subsection
  to appropriate values, specifically for these formats.
* The HEC format lets events overide many details on a per-event basis, such
  as the destination index. Use this value to read data which you know to be
  well-formatted and safe to index with little or no processing, such as
  data generated by locally written tools.
* When 'INDEXED_EXTRACTIONS = JSON' for a particular source type, do not also 
  set 'KV_MODE = json' for that source type. This causes the Splunk software to 
  extract the JSON fields twice: once at index time, and again at search time.
* Default: not set&lt;/LI-CODE&gt;&lt;P&gt;You can find more infos at&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.0/Admin/Propsconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.0.0/Admin/Propsconf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Mon, 15 Aug 2022 15:02:36 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2022-08-15T15:02:36Z</dc:date>
    <item>
      <title>Does a CSV import connector or a XML import connector exist in current Splunk versions?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-a-CSV-import-connector-or-a-XML-import-connector-exist-in/m-p/609492#M105671</link>
      <description>&lt;P&gt;Does a CSV import connector or a XML import connector exist in current Splunk versions?:)&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 13:43:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-a-CSV-import-connector-or-a-XML-import-connector-exist-in/m-p/609492#M105671</guid>
      <dc:creator>lwedekind</dc:creator>
      <dc:date>2022-08-15T13:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: Does a CSV import connector or a XML import connector exist in current Splunk versions?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-a-CSV-import-connector-or-a-XML-import-connector-exist-in/m-p/609497#M105673</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/248560"&gt;@lwedekind&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;there isn't a predefined connector, because Splunk doesn't use connectors.&lt;/P&gt;&lt;P&gt;But when you have to ingest a csv or a xml file, you have to configure in props.conf an option, called "INDEXED_EXTRACTIONS" and in this way the format is recognized.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;INDEXED_EXTRACTIONS = &amp;lt;CSV|TSV|PSV|W3C|JSON|HEC&amp;gt;
* The type of file that Splunk software should expect for a given source
  type, and the extraction and/or parsing method that should be used on the 
  file.
* The following values are valid for 'INDEXED_EXTRACTIONS':
  CSV  - Comma separated value format
  TSV  - Tab-separated value format
  PSV  - pipe ("|")-separated value format
  W3C  - World Wide Web Consortium (W3C) Extended Log File Format
  JSON - JavaScript Object Notation format
  HEC  - Interpret file as a stream of JSON events in the same format as the 
         HTTP Event Collector (HEC) input.
* These settings change the defaults for other settings in this subsection
  to appropriate values, specifically for these formats.
* The HEC format lets events overide many details on a per-event basis, such
  as the destination index. Use this value to read data which you know to be
  well-formatted and safe to index with little or no processing, such as
  data generated by locally written tools.
* When 'INDEXED_EXTRACTIONS = JSON' for a particular source type, do not also 
  set 'KV_MODE = json' for that source type. This causes the Splunk software to 
  extract the JSON fields twice: once at index time, and again at search time.
* Default: not set&lt;/LI-CODE&gt;&lt;P&gt;You can find more infos at&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.0/Admin/Propsconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.0.0/Admin/Propsconf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 15:02:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-a-CSV-import-connector-or-a-XML-import-connector-exist-in/m-p/609497#M105673</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-08-15T15:02:36Z</dc:date>
    </item>
  </channel>
</rss>

