<?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: Why is my table field from JSON not working on all fields? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440056#M76745</link>
    <description>&lt;P&gt;If you cannot provide a sanitized event of identical size, then there is no good way for us to help.&lt;/P&gt;</description>
    <pubDate>Thu, 03 Jan 2019 01:52:15 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2019-01-03T01:52:15Z</dc:date>
    <item>
      <title>Why is my table field from JSON not working on all fields?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440049#M76738</link>
      <description>&lt;P&gt;We are working with the following JSON generated by a dcos/marathon api:&lt;/P&gt;

&lt;P&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/6262i6C9E3B4020B2FE6B/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;When I run:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=dcos sourcetype="dcos:marathon:metrics" | table gauges.api.mesosphere.marathon.core.event.impl.stream.HttpEventStreamActorMetrics.number-of-streams.count
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I get a nice table with all the expected numbers. &lt;/P&gt;

&lt;P&gt;But, when I run: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=dcos sourcetype="dcos:marathon:metrics" | table gauges.service.mesosphere.marathon.leaderDuration.count
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;All the fields are empty.&lt;/P&gt;

&lt;P&gt;Why can I see the correct values for "gauges.api.mesosphere.marathon.core.event.impl.stream.HttpEventStreamActorMetrics.number-of-streams.count" But can not see it for gauges.service.mesosphere.marathon.leaderDuration.count&lt;BR /&gt;
I also tried to get the data with spath like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=dcos sourcetype="dcos:marathon:metrics" | spath "gauges.service.mesosphere.marathon.leaderDuration.count" |  table  *
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But again, the values are empty even though I can see gauges.service.mesosphere.marathon.leaderDuration.count in the table headings.&lt;/P&gt;

&lt;P&gt;Even when I generate the searches with Splunk I get no data&lt;/P&gt;

&lt;P&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/6263i57FE4060047C39F7/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Dec 2018 15:49:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440049#M76738</guid>
      <dc:creator>sboogaar</dc:creator>
      <dc:date>2018-12-18T15:49:40Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my table field from JSON not working on all fields?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440050#M76739</link>
      <description>&lt;P&gt;@sboogaar&lt;/P&gt;

&lt;P&gt;Can you please share the sample JSON event??&lt;/P&gt;</description>
      <pubDate>Tue, 18 Dec 2018 17:06:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440050#M76739</guid>
      <dc:creator>kamlesh_vaghela</dc:creator>
      <dc:date>2018-12-18T17:06:00Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my table field from JSON not working on all fields?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440051#M76740</link>
      <description>&lt;P&gt;Does splunk create a field name &lt;CODE&gt;gauges.service.mesosphere.marathon.leaderDuration.count&lt;/CODE&gt; similar to what it has created where it showed you the contents in the table. &lt;/P&gt;</description>
      <pubDate>Tue, 18 Dec 2018 17:21:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440051#M76740</guid>
      <dc:creator>macadminrohit</dc:creator>
      <dc:date>2018-12-18T17:21:34Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my table field from JSON not working on all fields?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440052#M76741</link>
      <description>&lt;P&gt;@macadminrohit  Yes see the last image.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Dec 2018 07:55:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440052#M76741</guid>
      <dc:creator>sboogaar</dc:creator>
      <dc:date>2018-12-19T07:55:46Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my table field from JSON not working on all fields?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440053#M76742</link>
      <description>&lt;P&gt;@kamlesh_vaghela It is 34k  characters long and contains private data so I can not share it, if you tell me what you want to check I will try to provide that information.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Dec 2018 08:52:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440053#M76742</guid>
      <dc:creator>sboogaar</dc:creator>
      <dc:date>2018-12-19T08:52:20Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my table field from JSON not working on all fields?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440054#M76743</link>
      <description>&lt;P&gt;@sboogaar&lt;BR /&gt;
I have a doubt regarding below configurations. It might be hit in your event. Can you please reconfigure limits.conf if required and check again.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;extraction_cutoff = &amp;lt;integer&amp;gt;
* For extract-all spath extraction mode, only apply extraction to the first
  &amp;lt;integer&amp;gt; number of bytes.
* Default: 5000
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Limitsconf#.5Bspath.5D"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Admin/Limitsconf#.5Bspath.5D&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;limit = &amp;lt;integer&amp;gt;
* The maximum number of fields that an automatic key-value field extraction
  (auto kv) can generate at search time.
* If search-time field extractions are disabled (KV_MODE=none in props.conf)
  then this setting determines the number of index-time fields that will be
  returned.
* The summary fields 'host', 'index', 'source', 'sourcetype', 'eventtype',
  'linecount', 'splunk_server', and 'splunk_server_group' do not count against
  this limit and will always be returned.
* Increase this setting if, for example, you have indexed data with a large
  number of columns and want to ensure that searches display all fields from
  the data.
* Default: 100
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Limitsconf#.5Bkv.5D"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Admin/Limitsconf#.5Bkv.5D&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Dec 2018 10:13:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440054#M76743</guid>
      <dc:creator>kamlesh_vaghela</dc:creator>
      <dc:date>2018-12-19T10:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my table field from JSON not working on all fields?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440055#M76744</link>
      <description>&lt;P&gt;Splunk has a limitation on how big a json it is able to extract.  &lt;/P&gt;

&lt;P&gt;Let's verify that is not the issue.  This should snip out all the nodes in the JSON before the leaderDuration node.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; index=dcos sourcetype="dcos:marathon:metrics" 
| head 1
| rex mode=sed field=_raw "s/(gauges:\s{)(.*)(service.mesosphere.marathon.leaderDuration)/\1\3/g"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Verify that that code kills the earlier data.  After that, try &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| table gauges.service.mesosphere.marathon.leaderDuration.count
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|  spath "gauges.service.mesosphere.marathon.leaderDuration.count"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 02 Jan 2019 17:38:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440055#M76744</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2019-01-02T17:38:10Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my table field from JSON not working on all fields?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440056#M76745</link>
      <description>&lt;P&gt;If you cannot provide a sanitized event of identical size, then there is no good way for us to help.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jan 2019 01:52:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440056#M76745</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-01-03T01:52:15Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my table field from JSON not working on all fields?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440057#M76746</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/127939"&gt;@kamlesh_vaghela&lt;/a&gt; changing the extraction_cutoff worked I did not need to update the limit. If you post it as an answer I will accept it.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 22:38:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440057#M76746</guid>
      <dc:creator>sboogaar</dc:creator>
      <dc:date>2020-09-29T22:38:37Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my table field from JSON not working on all fields?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440058#M76747</link>
      <description>&lt;P&gt;Great @sboogaar, extraction_cutoff  worked for you. &lt;BR /&gt;
Glad to help you.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jan 2019 09:48:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-table-field-from-JSON-not-working-on-all-fields/m-p/440058#M76747</guid>
      <dc:creator>kamlesh_vaghela</dc:creator>
      <dc:date>2019-01-03T09:48:24Z</dc:date>
    </item>
  </channel>
</rss>

