<?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: Still having to &amp;quot;SPATH&amp;quot; despite &amp;quot;INDEXED_EXTRACTIONS = json&amp;quot; being true? in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Still-having-to-quot-SPATH-quot-despite-quot-INDEXED-EXTRACTIONS/m-p/628039#M15192</link>
    <description>&lt;P&gt;There are three separate methods of handling json data - spath, auto_kv and indexed extractions. And each of them names fields differently as far as I remember. auto_kv "flattens" the json structure and gives you only leaf field names whereas spath creates field names from the whole object path. I think indexed extractions produce something more similar to auto_kv but I'm not 100% sure - I don't use it very often.&lt;/P&gt;</description>
    <pubDate>Mon, 23 Jan 2023 20:02:01 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2023-01-23T20:02:01Z</dc:date>
    <item>
      <title>Still having to "SPATH" despite "INDEXED_EXTRACTIONS = json" being true?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Still-having-to-quot-SPATH-quot-despite-quot-INDEXED-EXTRACTIONS/m-p/627833#M15178</link>
      <description>&lt;P&gt;These two pieces of SPL return two different-looking tables.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;index=servicenow sourcetype=incident number=INC5181781 
| spath opened_at
| spath resolved_at
| table number, opened_at, resolved_at, number, _time&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Will provide me with different results vs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;index=servicenow sourcetype=incident number=INC5181781 
| table number, opened_at, resolved_at, number, _time&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the one with "spath" the table has more values for those values for "opened_at" and "resolved_at". The same number of events are discovered, but the table makes it look like one event is "missing" dimensions.&lt;BR /&gt;&lt;BR /&gt;Even if I do these two search, and compare the "Selected Fields" section on the left hand side, the one with spath has more "events" that have the values.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the props.conf file the "source" has the line&lt;/P&gt;
&lt;P class=""&gt;&lt;SPAN class=""&gt;INDEXED_EXTRACTIONS = json&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;This may also be impacting my ability to search as well. It seems like I will not get complete results unless I do something like&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;sourcetype=incident
|spath number
|spath category
|search number=INC5181781 category=Closed&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I assume something is not configured as I expect it to be, and I am unsure where else to check.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Jan 2023 15:54:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Still-having-to-quot-SPATH-quot-despite-quot-INDEXED-EXTRACTIONS/m-p/627833#M15178</guid>
      <dc:creator>swangertyler</dc:creator>
      <dc:date>2023-01-23T15:54:36Z</dc:date>
    </item>
    <item>
      <title>Re: Still having to "SPATH" despite "INDEXED_EXTRACTIONS = json" being true</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Still-having-to-quot-SPATH-quot-despite-quot-INDEXED-EXTRACTIONS/m-p/627842#M15179</link>
      <description>&lt;P&gt;Can you share an example (sanitized) raw event?&amp;nbsp; It sounds like the event is not perfect JSON and so INDEXED_EXTRACTIONS is not extracting fields.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 22:06:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Still-having-to-quot-SPATH-quot-despite-quot-INDEXED-EXTRACTIONS/m-p/627842#M15179</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-01-20T22:06:51Z</dc:date>
    </item>
    <item>
      <title>Re: Still having to "SPATH" despite "INDEXED_EXTRACTIONS = json" being true</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Still-having-to-quot-SPATH-quot-despite-quot-INDEXED-EXTRACTIONS/m-p/628023#M15189</link>
      <description>&lt;P&gt;When I put the _raw event into something like&amp;nbsp;&lt;A href="https://jsonlint.com/" target="_blank"&gt;https://jsonlint.com/&lt;/A&gt;&amp;nbsp;it appears to be valid. However, I do know that a field in the original payload is a large text field, so it seems possible that something funny is happening.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I'll see if I can sanitize an event and get it posted here.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Jan 2023 18:35:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Still-having-to-quot-SPATH-quot-despite-quot-INDEXED-EXTRACTIONS/m-p/628023#M15189</guid>
      <dc:creator>swangertyler</dc:creator>
      <dc:date>2023-01-23T18:35:32Z</dc:date>
    </item>
    <item>
      <title>Re: Still having to "SPATH" despite "INDEXED_EXTRACTIONS = json" being true?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Still-having-to-quot-SPATH-quot-despite-quot-INDEXED-EXTRACTIONS/m-p/628039#M15192</link>
      <description>&lt;P&gt;There are three separate methods of handling json data - spath, auto_kv and indexed extractions. And each of them names fields differently as far as I remember. auto_kv "flattens" the json structure and gives you only leaf field names whereas spath creates field names from the whole object path. I think indexed extractions produce something more similar to auto_kv but I'm not 100% sure - I don't use it very often.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Jan 2023 20:02:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Still-having-to-quot-SPATH-quot-despite-quot-INDEXED-EXTRACTIONS/m-p/628039#M15192</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2023-01-23T20:02:01Z</dc:date>
    </item>
  </channel>
</rss>

