<?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 What is the best way to handle sequential event funnels? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/What-is-the-best-way-to-handle-sequential-event-funnels/m-p/11226#M713</link>
    <description>&lt;P&gt;Given a sequence of general to specific events (like product browsing a pages, followed by  particular product pages). What is the best way to bring information from the browse events into the results for the product event?&lt;/P&gt;

&lt;P&gt;&lt;B&gt;log example&lt;/B&gt;&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;PRE&gt;
 time=1 session=1 pageType=browse name=NewStuff resultsCount=3
 time=2 session=1 pageType=product product=a
 time=3 session=1 pageType=product product=b
&lt;/PRE&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;In the example a user hit a browse page with three products, and clicked through on two of them. I would like to transform those events into a table like this:&lt;/P&gt;

&lt;P&gt;&lt;B&gt;desire result&lt;/B&gt;&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;PRE&gt;
| session | srcBrowseName | Product |
| 1       | NewStuff      | a       |
| 1       | NewStuff      | b       |
&lt;/PRE&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;Notice that I have to repeat data from the browse event for each of the product page events. I have an inkling that this could be accomplished with a &lt;CODE&gt;subsearch&lt;/CODE&gt;, perhaps a subsearch of a &lt;CODE&gt;|transaction session startswith="pageType=browse"&lt;/CODE&gt;.&lt;/P&gt;</description>
    <pubDate>Sat, 10 Apr 2010 01:05:21 GMT</pubDate>
    <dc:creator>andynu</dc:creator>
    <dc:date>2010-04-10T01:05:21Z</dc:date>
    <item>
      <title>What is the best way to handle sequential event funnels?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-the-best-way-to-handle-sequential-event-funnels/m-p/11226#M713</link>
      <description>&lt;P&gt;Given a sequence of general to specific events (like product browsing a pages, followed by  particular product pages). What is the best way to bring information from the browse events into the results for the product event?&lt;/P&gt;

&lt;P&gt;&lt;B&gt;log example&lt;/B&gt;&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;PRE&gt;
 time=1 session=1 pageType=browse name=NewStuff resultsCount=3
 time=2 session=1 pageType=product product=a
 time=3 session=1 pageType=product product=b
&lt;/PRE&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;In the example a user hit a browse page with three products, and clicked through on two of them. I would like to transform those events into a table like this:&lt;/P&gt;

&lt;P&gt;&lt;B&gt;desire result&lt;/B&gt;&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;PRE&gt;
| session | srcBrowseName | Product |
| 1       | NewStuff      | a       |
| 1       | NewStuff      | b       |
&lt;/PRE&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;Notice that I have to repeat data from the browse event for each of the product page events. I have an inkling that this could be accomplished with a &lt;CODE&gt;subsearch&lt;/CODE&gt;, perhaps a subsearch of a &lt;CODE&gt;|transaction session startswith="pageType=browse"&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Sat, 10 Apr 2010 01:05:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-the-best-way-to-handle-sequential-event-funnels/m-p/11226#M713</guid>
      <dc:creator>andynu</dc:creator>
      <dc:date>2010-04-10T01:05:21Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best way to handle sequential event funnels?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-the-best-way-to-handle-sequential-event-funnels/m-p/11227#M714</link>
      <description>&lt;P&gt;Maybe:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;pageType=product | join session usetime=true earliest=true [ pageType=browse | fields - resultsCount ]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;is something like what you need?&lt;/P&gt;</description>
      <pubDate>Sat, 10 Apr 2010 04:32:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-the-best-way-to-handle-sequential-event-funnels/m-p/11227#M714</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-04-10T04:32:13Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best way to handle sequential event funnels?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-is-the-best-way-to-handle-sequential-event-funnels/m-p/11228#M715</link>
      <description>&lt;P&gt;Thanks! &lt;/P&gt;

&lt;P&gt;pageType=product |join session usetime=t earlier=t [search pageType=browse | fields + resultCount]&lt;/P&gt;

&lt;P&gt;Unfortunately |join seems to be very particular about which types of fields it will work on, some of my fields that in independent searches extracted matching field values did not work as the join parameter.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Apr 2010 00:20:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-is-the-best-way-to-handle-sequential-event-funnels/m-p/11228#M715</guid>
      <dc:creator>andynu</dc:creator>
      <dc:date>2010-04-14T00:20:09Z</dc:date>
    </item>
  </channel>
</rss>

