<?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: piping in splunk in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63744#M717</link>
    <description>&lt;P&gt;"|" This is a pipe&lt;/P&gt;

&lt;P&gt;&lt;IMG src="http://3.bp.blogspot.com/_alwOwaia_T0/THvP4FPFPnI/AAAAAAAAAlo/CBulpuCSBQM/s1600/ceci-n-est-pas-une-pipe.jpg" alt="alt text" /&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Sep 2012 17:25:09 GMT</pubDate>
    <dc:creator>yannK</dc:creator>
    <dc:date>2012-09-18T17:25:09Z</dc:date>
    <item>
      <title>piping in splunk</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63742#M715</link>
      <description>&lt;P&gt;Hello All, &lt;/P&gt;

&lt;P&gt;Does anyone know how piping in splunk is performed. I tried to search for information on this subject but unfortunately I am unable to find anything on it. My question is: does it take the search results from the buffer and then searches on it when piping is done. &lt;/P&gt;

&lt;P&gt;To clarify if I search for host="some_host" | source="testing_source" does splunk first search for some host and then from that buffer searches for the source testing_source on it. OR does it search for some_host and then when you pipe it searches again from the entire buffer?&lt;/P&gt;

&lt;P&gt;The main purpose of this question is performance. &lt;/P&gt;

&lt;P&gt;Thank you for all your help!&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 12:27:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63742#M715</guid>
      <dc:creator>nowakdaw</dc:creator>
      <dc:date>2020-09-28T12:27:36Z</dc:date>
    </item>
    <item>
      <title>Re: piping in splunk</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63743#M716</link>
      <description>&lt;P&gt;this article in the documentation provides an overview of how the search pipeline works:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/User/HowSearchCommandsWork"&gt;http://docs.splunk.com/Documentation/Splunk/latest/User/HowSearchCommandsWork&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;here is a relevant snippet:&lt;/P&gt;

&lt;P&gt;"The "search pipeline" refers to the structure of a Splunk search, in which consecutive commands are chained together using a pipe character that tells Splunk to &lt;STRONG&gt;use the output or result of one command as the input for the next command&lt;/STRONG&gt;."&lt;/P&gt;

&lt;P&gt;your first interpretation is correct--the goal here is to filter down your results set as much as possible before performing calculations or other actions on the final set of results.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2012 17:20:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63743#M716</guid>
      <dc:creator>piebob</dc:creator>
      <dc:date>2012-09-18T17:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: piping in splunk</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63744#M717</link>
      <description>&lt;P&gt;"|" This is a pipe&lt;/P&gt;

&lt;P&gt;&lt;IMG src="http://3.bp.blogspot.com/_alwOwaia_T0/THvP4FPFPnI/AAAAAAAAAlo/CBulpuCSBQM/s1600/ceci-n-est-pas-une-pipe.jpg" alt="alt text" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2012 17:25:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63744#M717</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2012-09-18T17:25:09Z</dc:date>
    </item>
    <item>
      <title>Re: piping in splunk</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63745#M718</link>
      <description>&lt;P&gt;Note that your pipe example is syntactically incorrect - you need a command after the pipe. What you've done is added another search filter after the pipe. This filter should be part of the search command before the pipe instead.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2012 18:21:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63745#M718</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-09-18T18:21:25Z</dc:date>
    </item>
    <item>
      <title>Re: piping in splunk</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63746#M719</link>
      <description>&lt;P&gt;Yes! I apologize for my carelessness. Thank you for pointing that out.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2012 18:27:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63746#M719</guid>
      <dc:creator>nowakdaw</dc:creator>
      <dc:date>2012-09-18T18:27:46Z</dc:date>
    </item>
    <item>
      <title>Re: piping in splunk</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63747#M720</link>
      <description>&lt;P&gt;Current doc link: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.1/Search/Aboutsearchlanguagesyntax#About_the_search_pipeline"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.1/Search/Aboutsearchlanguagesyntax#About_the_search_pipeline&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 05 Dec 2015 17:16:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63747#M720</guid>
      <dc:creator>ChrisG</dc:creator>
      <dc:date>2015-12-05T17:16:13Z</dc:date>
    </item>
    <item>
      <title>Re: piping in splunk</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63748#M721</link>
      <description>&lt;P&gt;What if I don't want to pipe my results, i.e I want each eval to be performed on the entire buffer and not just the subset?&lt;/P&gt;

&lt;P&gt;For example:&lt;BR /&gt;
eval successful_transitions = case(searchmatch("CASE(ActiveSuccesses)"),"active",searchmatch("CASE(InactiveSuccesses)"),"inactive")&lt;BR /&gt;
  | stats count as successes by successful_transitions&lt;BR /&gt;
  | eval failed_transitions = case(searchmatch("[active-failure]"),"active",searchmatch("[inactive-failure]"),"inactive")&lt;BR /&gt;
  | stats count as failures by failed_transitions&lt;/P&gt;

&lt;P&gt;Here I want to find, of all the events, How many events are active/inactive successful and how many are active/inactive failed??&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 17:24:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/piping-in-splunk/m-p/63748#M721</guid>
      <dc:creator>vdeshpandegrp</dc:creator>
      <dc:date>2020-09-29T17:24:27Z</dc:date>
    </item>
  </channel>
</rss>

