<?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: Drilldown not working with Join Command in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Drilldown-not-working-with-Join-Command/m-p/21547#M3541</link>
    <description>&lt;P&gt;In order to work around this limitation, I had to leverage Sideview Utils &lt;CODE&gt;Redirector&lt;/CODE&gt; component to build a custom search &lt;CODE&gt;url&lt;/CODE&gt; to support the drill down behavior. The other gotcha was creating &lt;STRONG&gt;event types&lt;/STRONG&gt; for each join duration type so that the drill down could filter by the proper bucket.&lt;/P&gt;

&lt;P&gt;After removing the default &lt;CODE&gt;ConvertToDrilldownSearch&lt;/CODE&gt; module, here is the stub of the &lt;CODE&gt;Redirector&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;
&lt;MODULE name="FlashChart"&gt;
    &lt;MODULE name="Redirector"&gt;
        &lt;OBJECT&gt;&lt;PARAM name="popup" /&gt;True
        &lt;PARAM name="url" /&gt;flashtimeline
        &lt;PARAM name="arg.q" /&gt;search index="myIndex" host=myHost username="$click.value$" eventtype="#$click.name2$" | stats values(cs_uri_stem) as "Pages Accessed", count as "[Pages Viewed $click.name2$]" by  username" 
    &lt;/OBJECT&gt;&lt;/MODULE&gt;
&lt;/MODULE&gt;
&lt;/PRE&gt;    

&lt;P&gt;The biggest let down of using the splunk markup is that their is no easy way to do conditionals inside a param - or performing an inline evaluation. Maybe this is just my lack of know-how. I've also learned that &lt;CODE&gt;ConvertToIntention&lt;/CODE&gt; is completely useless when you need complete control over the search query (&lt;EM&gt;e.g. q=search index=myIndex&lt;/EM&gt;). Stick with SideView Utils &lt;CODE&gt;Redirector&lt;/CODE&gt; if you need complete search query control.&lt;/P&gt;</description>
    <pubDate>Wed, 07 Nov 2012 07:08:20 GMT</pubDate>
    <dc:creator>slierninja</dc:creator>
    <dc:date>2012-11-07T07:08:20Z</dc:date>
    <item>
      <title>Drilldown not working with Join Command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Drilldown-not-working-with-Join-Command/m-p/21546#M3540</link>
      <description>&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/64069/grouping-aggregate-queries-together/64075"&gt;I figured out how to create monthly buckets using the &lt;CODE&gt;join&lt;/CODE&gt; command&lt;/A&gt;, but now I cannot drilldown into my results. Can someone help me figure out how to rewrite my query or enable drilldowns using the &lt;CODE&gt;join&lt;/CODE&gt; command?&lt;/P&gt;

&lt;H3&gt;Splunk Error Message&lt;/H3&gt;

&lt;P&gt;&lt;EM&gt;Encountered an unexpected error while parsing intentions.&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;
&lt;EM&gt;PARSER: Applying intentions failed Unable to drilldown because of post-reporting 'join' command&lt;/EM&gt;.&lt;/P&gt;

&lt;H3&gt;Query&lt;/H3&gt;

&lt;PRE&gt;
index="myIndex" host=myHost daysago=30 | stats Count as 30Days by username | 
join username [search index="myIndex" host=myHost daysago=60 | stats Count as 60Days by username] | join username [search index="myIndex" host=myHost daysago=90 | stats Count as 90Days by username] | join username [search index="myIndex" host=myHost daysago=120 | stats Count as 120Days by username]|fields username, 30Days, 60Days, 90Days, 120Days
&lt;/PRE&gt;</description>
      <pubDate>Fri, 02 Nov 2012 14:38:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Drilldown-not-working-with-Join-Command/m-p/21546#M3540</guid>
      <dc:creator>slierninja</dc:creator>
      <dc:date>2012-11-02T14:38:33Z</dc:date>
    </item>
    <item>
      <title>Re: Drilldown not working with Join Command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Drilldown-not-working-with-Join-Command/m-p/21547#M3541</link>
      <description>&lt;P&gt;In order to work around this limitation, I had to leverage Sideview Utils &lt;CODE&gt;Redirector&lt;/CODE&gt; component to build a custom search &lt;CODE&gt;url&lt;/CODE&gt; to support the drill down behavior. The other gotcha was creating &lt;STRONG&gt;event types&lt;/STRONG&gt; for each join duration type so that the drill down could filter by the proper bucket.&lt;/P&gt;

&lt;P&gt;After removing the default &lt;CODE&gt;ConvertToDrilldownSearch&lt;/CODE&gt; module, here is the stub of the &lt;CODE&gt;Redirector&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;
&lt;MODULE name="FlashChart"&gt;
    &lt;MODULE name="Redirector"&gt;
        &lt;OBJECT&gt;&lt;PARAM name="popup" /&gt;True
        &lt;PARAM name="url" /&gt;flashtimeline
        &lt;PARAM name="arg.q" /&gt;search index="myIndex" host=myHost username="$click.value$" eventtype="#$click.name2$" | stats values(cs_uri_stem) as "Pages Accessed", count as "[Pages Viewed $click.name2$]" by  username" 
    &lt;/OBJECT&gt;&lt;/MODULE&gt;
&lt;/MODULE&gt;
&lt;/PRE&gt;    

&lt;P&gt;The biggest let down of using the splunk markup is that their is no easy way to do conditionals inside a param - or performing an inline evaluation. Maybe this is just my lack of know-how. I've also learned that &lt;CODE&gt;ConvertToIntention&lt;/CODE&gt; is completely useless when you need complete control over the search query (&lt;EM&gt;e.g. q=search index=myIndex&lt;/EM&gt;). Stick with SideView Utils &lt;CODE&gt;Redirector&lt;/CODE&gt; if you need complete search query control.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Nov 2012 07:08:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Drilldown-not-working-with-Join-Command/m-p/21547#M3541</guid>
      <dc:creator>slierninja</dc:creator>
      <dc:date>2012-11-07T07:08:20Z</dc:date>
    </item>
  </channel>
</rss>

