<?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: multiple subsearch using appendpipe in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269839#M190016</link>
    <description>&lt;P&gt;That worked absolutely perfect.&lt;/P&gt;</description>
    <pubDate>Tue, 13 Oct 2015 01:49:17 GMT</pubDate>
    <dc:creator>ljohnson_possib</dc:creator>
    <dc:date>2015-10-13T01:49:17Z</dc:date>
    <item>
      <title>multiple subsearch using appendpipe</title>
      <link>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269834#M190011</link>
      <description>&lt;P&gt;I am trying to create a search that will give a table displaying counts for multiple time_taken intervals. For example I want to display the counts for calls with a time_taken of 0, time_taken between 1 and 15, time_taken between 16 and 30, time_taken between 31 and 45, time_taken between 46 and 60.......time_taken greater than 300.&lt;/P&gt;

&lt;P&gt;Here is the search I have been playing around with to no avail:&lt;/P&gt;

&lt;P&gt;|stats avg(time_taken) as Scenario count(eval(time_taken =0)) as Count | eval Scenario = "Calls returning in 0 time"&lt;BR /&gt;
|appendpipe [stats count(eval(time_taken &amp;gt; 0 AND time_taken &amp;lt;= 15)) as Count | eval Scenario = "Calls returning between 1 and 15 time"]&lt;BR /&gt;
|appendpipe [stats count(eval(time_taken &amp;gt; 16 AND time_taken &amp;lt;= 30)) as Count | eval Scenario = "Calls returning between 16 and 30 time"]&lt;BR /&gt;
|appendpipe [stats count(eval(time_taken &amp;gt; 31 AND time_taken &amp;lt;= 45)) as Count | eval Scenario = "Calls returning between 31 and 45 time"]&lt;BR /&gt;
|appendpipe [stats count(eval(time_taken &amp;gt; 46 AND time_taken &amp;lt;= 60)) as Count | eval Scenario = "Calls returning between 46 and 60 time"]&lt;BR /&gt;
|appendpipe [stats count(eval(time_taken &amp;gt; 61 AND time_taken &amp;lt;= 100)) as Count | eval Scenario = "Calls returning between 61 and 100 time"]&lt;BR /&gt;
|appendpipe [stats count(eval(time_taken &amp;gt; 101 AND time_taken &amp;lt;= 200)) as Count | eval Scenario = "Calls returning between 101 and 200 time"]&lt;BR /&gt;
|appendpipe [stats count(eval(time_taken &amp;gt; 201 AND time_taken &amp;lt;= 300)) as Count | eval Scenario = "Calls returning between 201 and 300 time"]&lt;BR /&gt;
|appendpipe [stats count(eval(time_taken &amp;gt; 300)) as Count | eval Scenario = "Calls returning more than 300"]&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 07:33:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269834#M190011</guid>
      <dc:creator>ljohnson_possib</dc:creator>
      <dc:date>2020-09-29T07:33:00Z</dc:date>
    </item>
    <item>
      <title>Re: multiple subsearch using appendpipe</title>
      <link>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269835#M190012</link>
      <description>&lt;P&gt;First of all, your &lt;CODE&gt;eval Scenario=&lt;/CODE&gt; is clobbering your &lt;CODE&gt;as Scenario&lt;/CODE&gt; so you are losing your main data element.  Second, you really don't need to append anything.  Give this a try:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|stats avg(time_taken) as Scenario
count(eval(time_taken =0)) as "Calls returning in 0 time" 
count(eval(time_taken &amp;gt; 0 AND time_taken &amp;lt;= 15)) as "Calls returning between 1 and 15 time"
count(eval(time_taken &amp;gt; 16 AND time_taken &amp;lt;= 30)) as "Calls returning between 16 and 30 time"
count(eval(time_taken &amp;gt; 31 AND time_taken &amp;lt;= 45)) as "Calls returning between 31 and 45 time"
count(eval(time_taken &amp;gt; 46 AND time_taken &amp;lt;= 60)) as "Calls returning between 46 and 60 time"
count(eval(time_taken &amp;gt; 61 AND time_taken &amp;lt;= 100)) as "Calls returning between 61 and 100 time"
count(eval(time_taken &amp;gt; 101 AND time_taken &amp;lt;= 200)) as "Calls returning between 101 and 200 time"
count(eval(time_taken &amp;gt; 201 AND time_taken &amp;lt;= 300)) as "Calls returning between 201 and 300 time"
count(eval(time_taken &amp;gt; 300)) as "Calls returning more than 300"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 12 Oct 2015 16:53:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269835#M190012</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-10-12T16:53:23Z</dc:date>
    </item>
    <item>
      <title>Re: multiple subsearch using appendpipe</title>
      <link>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269836#M190013</link>
      <description>&lt;P&gt;Thanks...this logic got the main data needed for the dashboard I am building. Something I haven't had since I began a week ago.  The results are given all on a single row (one line of output). I am hoping to have the results in one column. This way I can use the pie chart in my dash. &lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2015 17:15:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269836#M190013</guid>
      <dc:creator>ljohnson_possib</dc:creator>
      <dc:date>2015-10-12T17:15:24Z</dc:date>
    </item>
    <item>
      <title>Re: multiple subsearch using appendpipe</title>
      <link>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269837#M190014</link>
      <description>&lt;P&gt;By the way woodcock thanks a million for the answer. If I cannot get my pie chart to work, I will find a way to make the one line result work in the dashboard.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2015 17:16:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269837#M190014</guid>
      <dc:creator>ljohnson_possib</dc:creator>
      <dc:date>2015-10-12T17:16:31Z</dc:date>
    </item>
    <item>
      <title>Re: multiple subsearch using appendpipe</title>
      <link>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269838#M190015</link>
      <description>&lt;P&gt;For a 1 column, just add this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | transpose
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 13 Oct 2015 00:03:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269838#M190015</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-10-13T00:03:27Z</dc:date>
    </item>
    <item>
      <title>Re: multiple subsearch using appendpipe</title>
      <link>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269839#M190016</link>
      <description>&lt;P&gt;That worked absolutely perfect.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Oct 2015 01:49:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/multiple-subsearch-using-appendpipe/m-p/269839#M190016</guid>
      <dc:creator>ljohnson_possib</dc:creator>
      <dc:date>2015-10-13T01:49:17Z</dc:date>
    </item>
  </channel>
</rss>

