Well, my recommendation is to move a bit more in the Sideview Utils direction and use the Sideview Redirector module in place of the Splunk modules ConvertToDrilldownSearch and ViewRedirector.
Here's a simple example using the Sideview Table module. Note that you can also use the Splunk modules SimpleResultsTable, JSChart or FlashChart. If you need to use FlashChart or JSChart though make sure you're using a relatively recent copy of Sideview Utils (older versions didn't provide key patches to JSChart and will be missing some other fixes).
<module name="Search" layoutPanel="panel_row1_col1" autoRun="True">
<param name="search">index=_internal source="*metrics.log" group="per_sourcetype_thruput" | stats avg(eps) by series | sort - avg(eps)</param>
<param name="earliest">-12h</param>
<module name="Pager">
<module name="Table">
<module name="Redirector">
<param name="url">flashtimeline</param>
<param name="arg.q">search index=_internal source="*metrics.log" group="per_sourcetype_thruput" $click.searchTerms$</param>
<param name="arg.earliest">$search.timeRange.earliest$</param>
<param name="arg.latest">$search.timeRange.latest$</param>
</module>
</module>
</module>
</module>
As you can see Redirector is a little flatter and dumber. You're literally specifying the individual querystring arguments and telling it what URL to go to, as opposed to using ConvertToDrilldownSearch and ViewRedirector where there's more magic going on, (some of which involves intentions).
There are other ways you can use Redirector, and there's some advanced functionality around its "generalSearchTermField" and "autoDrilldown" field, but these are only for when you're letting the user type in any splunk search and therefore the system has to figure out whether it's a drilldown on a timechart, or a stats, or top, or plain-events... Don't worry about those two params unless you start doing that sort of really advanced stuff.
... View more
