<?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 Are wildcards supported for JSON? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Are-wildcards-supported-for-JSON/m-p/355577#M64981</link>
    <description>&lt;P&gt;I've used the HEC to index some json data that looks kind of like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{
    "FieldA_sec": 0.12443,
    "FieldB_sec": 0.10392,
    "FieldC_sec": 0.30292
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However these two queries give different results:  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| stats avg(FieldA_sec) as FieldA_sec_avg, avg(FieldB_sec) as FieldB_sec_avg, avg(FieldC_sec) as FieldC_sec_avg
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This query works as expected.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| stats avg(*_sec) as *_sec_avg
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This returns the average for only one of my fields.&lt;/P&gt;

&lt;P&gt;When inspecting the search log, I found that only some of my fields showed up in the field summary.&lt;BR /&gt;
The field summary contained 112 fields, but should have over 300 fields.&lt;/P&gt;

&lt;P&gt;Is there a limit to the numbers of columns that will be matched in a wildcard when using JSON events?&lt;/P&gt;</description>
    <pubDate>Thu, 15 Mar 2018 20:42:38 GMT</pubDate>
    <dc:creator>chustar</dc:creator>
    <dc:date>2018-03-15T20:42:38Z</dc:date>
    <item>
      <title>Are wildcards supported for JSON?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Are-wildcards-supported-for-JSON/m-p/355577#M64981</link>
      <description>&lt;P&gt;I've used the HEC to index some json data that looks kind of like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{
    "FieldA_sec": 0.12443,
    "FieldB_sec": 0.10392,
    "FieldC_sec": 0.30292
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However these two queries give different results:  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| stats avg(FieldA_sec) as FieldA_sec_avg, avg(FieldB_sec) as FieldB_sec_avg, avg(FieldC_sec) as FieldC_sec_avg
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This query works as expected.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| stats avg(*_sec) as *_sec_avg
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This returns the average for only one of my fields.&lt;/P&gt;

&lt;P&gt;When inspecting the search log, I found that only some of my fields showed up in the field summary.&lt;BR /&gt;
The field summary contained 112 fields, but should have over 300 fields.&lt;/P&gt;

&lt;P&gt;Is there a limit to the numbers of columns that will be matched in a wildcard when using JSON events?&lt;/P&gt;</description>
      <pubDate>Thu, 15 Mar 2018 20:42:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Are-wildcards-supported-for-JSON/m-p/355577#M64981</guid>
      <dc:creator>chustar</dc:creator>
      <dc:date>2018-03-15T20:42:38Z</dc:date>
    </item>
  </channel>
</rss>

