<?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: Splunk 6 query format for JSON data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-6-query-format-for-JSON-data/m-p/103028#M21643</link>
    <description>&lt;P&gt;What's happened is that the "spath" has become silent as the extractions are now automatic...&lt;/P&gt;

&lt;P&gt;&lt;B&gt;click on the field in the fields list rather than the value in the event.&lt;BR /&gt;
and select the value you want, in this case:&lt;BR /&gt; Field: level &lt;BR /&gt;  Value: info &lt;/B&gt;&lt;/P&gt;

&lt;P&gt;You should see:  &lt;B&gt;level = info&lt;/B&gt; in the search box&lt;/P&gt;

&lt;P&gt;This now behaves like any other field, regardless of the format of the raw events.&lt;/P&gt;

&lt;P&gt;Clicking on the event text also behaves like any other event regardless of the origins. Of course we maintain the JSON formatting for you in the raw view because JSON has the formatting directives... &lt;/P&gt;</description>
    <pubDate>Sat, 09 Nov 2013 19:38:53 GMT</pubDate>
    <dc:creator>rsennett_splunk</dc:creator>
    <dc:date>2013-11-09T19:38:53Z</dc:date>
    <item>
      <title>Splunk 6 query format for JSON data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-6-query-format-for-JSON-data/m-p/103027#M21642</link>
      <description>&lt;P&gt;We send JSON formatted data into Splunk. On upgrading to Splunk 6 I noticed that selecting the value of a JSON field no longer filters the query with an spath automatically. &lt;BR /&gt;
For instance if the JSON data was&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{
  level : "Info",
  message : "xxxx"
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and one clicked on "Info"&lt;BR /&gt;
in Splunk 5 the query would become&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="x" | spath "level" | search "level"="Info"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;While in Splunk 6 it becomes&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="x"  Info
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Is there a way to retain the behavior of Splunk 5?&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2013 02:53:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-6-query-format-for-JSON-data/m-p/103027#M21642</guid>
      <dc:creator>amanteja</dc:creator>
      <dc:date>2013-10-17T02:53:43Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk 6 query format for JSON data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-6-query-format-for-JSON-data/m-p/103028#M21643</link>
      <description>&lt;P&gt;What's happened is that the "spath" has become silent as the extractions are now automatic...&lt;/P&gt;

&lt;P&gt;&lt;B&gt;click on the field in the fields list rather than the value in the event.&lt;BR /&gt;
and select the value you want, in this case:&lt;BR /&gt; Field: level &lt;BR /&gt;  Value: info &lt;/B&gt;&lt;/P&gt;

&lt;P&gt;You should see:  &lt;B&gt;level = info&lt;/B&gt; in the search box&lt;/P&gt;

&lt;P&gt;This now behaves like any other field, regardless of the format of the raw events.&lt;/P&gt;

&lt;P&gt;Clicking on the event text also behaves like any other event regardless of the origins. Of course we maintain the JSON formatting for you in the raw view because JSON has the formatting directives... &lt;/P&gt;</description>
      <pubDate>Sat, 09 Nov 2013 19:38:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-6-query-format-for-JSON-data/m-p/103028#M21643</guid>
      <dc:creator>rsennett_splunk</dc:creator>
      <dc:date>2013-11-09T19:38:53Z</dc:date>
    </item>
  </channel>
</rss>

