<?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: Subsearch issue with specified fields in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108661#M28307</link>
    <description>&lt;P&gt;That's great that you got it working, but there's really no need to rewrite the search like that - &lt;CODE&gt;format&lt;/CODE&gt; is called implicitly at the end of a subsearch anyway, and &lt;CODE&gt;table&lt;/CODE&gt; is possibly worse performance-wise than &lt;CODE&gt;fields&lt;/CODE&gt;.&lt;/P&gt;</description>
    <pubDate>Tue, 30 Jul 2013 09:00:28 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2013-07-30T09:00:28Z</dc:date>
    <item>
      <title>Subsearch issue with specified fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108657#M28303</link>
      <description>&lt;P&gt;Hi &lt;/P&gt;

&lt;P&gt;I would like to get all sourcetypes for a specific app, which have normaly one index.&lt;BR /&gt;
So I tried this search&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal group=per_sourcetype_thruput series=[|metadata type=sourcetypes index=itm | table sourcetype | format]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;but it seems that I cant use the series field directly.&lt;BR /&gt;
Is this generaly possible or have I do escape the field for that?&lt;/P&gt;

&lt;P&gt;Thanks&lt;BR /&gt;
Rob&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2013 13:58:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108657#M28303</guid>
      <dc:creator>RobertRi</dc:creator>
      <dc:date>2013-07-29T13:58:13Z</dc:date>
    </item>
    <item>
      <title>Re: Subsearch issue with specified fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108658#M28304</link>
      <description>&lt;P&gt;you can use sideview utils to do that&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2013 13:58:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108658#M28304</guid>
      <dc:creator>ddarmand</dc:creator>
      <dc:date>2013-07-29T13:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Subsearch issue with specified fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108659#M28305</link>
      <description>&lt;P&gt;That will cause a syntax error because the string returned by the subsearch is formatted somewhat differently - you can see exactly how it's formatted by running the subsearch on its own, including the ending &lt;CODE&gt;format&lt;/CODE&gt; command.&lt;/P&gt;

&lt;P&gt;You could fix this by specifying arguments to &lt;CODE&gt;format&lt;/CODE&gt;, but a better option would be to just rename your sourcetype field in the subsearch to series.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal group=per_sourcetype_thruput [|metadata type=sourcetypes index=itm | rename sourcetype as series | fields series]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 29 Jul 2013 14:47:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108659#M28305</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-07-29T14:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: Subsearch issue with specified fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108660#M28306</link>
      <description>&lt;P&gt;thanks that work&lt;/P&gt;

&lt;P&gt;and this with a small change too &lt;/P&gt;

&lt;P&gt;index=_internal group=per_sourcetype_thruput [|metadata type=sourcetypes index=itm | table sourcetype | rename sourcetype AS series | format]&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:27:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108660#M28306</guid>
      <dc:creator>RobertRi</dc:creator>
      <dc:date>2020-09-28T14:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Subsearch issue with specified fields</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108661#M28307</link>
      <description>&lt;P&gt;That's great that you got it working, but there's really no need to rewrite the search like that - &lt;CODE&gt;format&lt;/CODE&gt; is called implicitly at the end of a subsearch anyway, and &lt;CODE&gt;table&lt;/CODE&gt; is possibly worse performance-wise than &lt;CODE&gt;fields&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2013 09:00:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Subsearch-issue-with-specified-fields/m-p/108661#M28307</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-07-30T09:00:28Z</dc:date>
    </item>
  </channel>
</rss>

