<?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: Single Value fields Ingested as Multi Value in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412293#M94233</link>
    <description>&lt;P&gt;Do you have multiple extraction methods defined?&lt;/P&gt;

&lt;P&gt;Such as using indexed_extractions and kv_mode?&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 20:56:20 GMT</pubDate>
    <dc:creator>jkat54</dc:creator>
    <dc:date>2020-09-29T20:56:20Z</dc:date>
    <item>
      <title>Single Value fields Ingested as Multi Value</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412292#M94232</link>
      <description>&lt;P&gt;I never ran into this problem before, but I hope someone has..&lt;/P&gt;

&lt;P&gt;I have a python script which calls a REST API and passes the JSON to Splunk via the HEC.&lt;BR /&gt;
The fields are single-valued, however, Splunk converts them to multi-value.&lt;BR /&gt;
&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/5584i4D93171026821A6A/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Does anyone know why this is happening and how to fix it?&lt;/P&gt;</description>
      <pubDate>Sat, 18 Aug 2018 15:06:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412292#M94232</guid>
      <dc:creator>fdarrigo</dc:creator>
      <dc:date>2018-08-18T15:06:27Z</dc:date>
    </item>
    <item>
      <title>Re: Single Value fields Ingested as Multi Value</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412293#M94233</link>
      <description>&lt;P&gt;Do you have multiple extraction methods defined?&lt;/P&gt;

&lt;P&gt;Such as using indexed_extractions and kv_mode?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 20:56:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412293#M94233</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2020-09-29T20:56:20Z</dc:date>
    </item>
    <item>
      <title>Re: Single Value fields Ingested as Multi Value</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412294#M94234</link>
      <description>&lt;P&gt;No I don't&lt;/P&gt;</description>
      <pubDate>Sat, 18 Aug 2018 16:25:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412294#M94234</guid>
      <dc:creator>fdarrigo</dc:creator>
      <dc:date>2018-08-18T16:25:42Z</dc:date>
    </item>
    <item>
      <title>Re: Single Value fields Ingested as Multi Value</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412295#M94235</link>
      <description>&lt;P&gt;Can you provide a data sample and the sourcetype you’re using?&lt;/P&gt;</description>
      <pubDate>Sat, 18 Aug 2018 16:50:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412295#M94235</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2018-08-18T16:50:40Z</dc:date>
    </item>
    <item>
      <title>Re: Single Value fields Ingested as Multi Value</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412296#M94236</link>
      <description>&lt;P&gt;Set &lt;CODE&gt;KV_MODE&lt;/CODE&gt; to &lt;CODE&gt;NONE&lt;/CODE&gt; and it will go away.  Actually a value of &lt;CODE&gt;AUTO&lt;/CODE&gt; might be better but the real problem is that right now it is set to &lt;CODE&gt;JSON&lt;/CODE&gt; which is wrong because then you are parsing the &lt;CODE&gt;JSON&lt;/CODE&gt; twice.   This is &lt;EM&gt;definitely&lt;/EM&gt; the problem.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Aug 2018 19:46:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Single-Value-fields-Ingested-as-Multi-Value/m-p/412296#M94236</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2018-08-20T19:46:09Z</dc:date>
    </item>
  </channel>
</rss>

