1) The main problem here, is that the second search and chart modules are not downstream from the chart being clicked on. In the Sideview XML, the only way a module gets any information from another module is if it is downstream from that module. So as this XML is written, these two charts are completely independent.
Solution: Nest the Search + HiddenChartFormatter + JSChart inside (ie downstream) from the first JSChart.
2) After that though, there's a second mistake being made here. In inline drilldown, the timerange is actually calculated from the timechart click for you automatically, so you don't have to do anything at all. In fact if we only fixed prolem #1, then the way you are setting earliest/latest here is actually going to replace the valid earliest and latest bounds of the automatically-determined timerange, and instead set them to null values.
Solution: delete these lines:
<param name="earliest">$earliest$</param>
<param name="latest">$latest$</param>
and the drilldown timerange will get passed down.
Some other minor items
3) it's weird to be using the $foo.rawValue$ tokens here instead of simply using the $foo$ tokens. The docs discuss the rawValue tokens, and say that they are only for when you are passing the token into a URL with the Redirector module, constructing a URL manually with the HTML module, or displaying the value to the user on screen. For all other uses, you really do want the $query$ and $function$ tokens here, not $query.rawValue$ and $function.rawValue$. It's probably doing no harm but it doesn't take long to hit a case where there's a problem using a rawValue unnecessarily.
4) Once the drilldown modules are properly nested, you can actually factor most of this HiddenChartFormatter keys up a level so you only specify them once and thus save some XML. You can also use the Sideview ValueSetter module to replace HiddenChartFormatter. I find HiddenChartFormatter very confusing, as some keys like "legend.placement" allow you to omit the "charting." prefix, and other keys do not. With ValueSetter you need an extra "arg." on the front, but at least you can set all charting keys the same with "arg.charting.". The ValueSetter is also a very useful module for lots of other corner cases, whereas the HiddenChartFormatter is useful only for charting.
Doing all of this, here is modified XML. I also have some conventions for whitespace and indentation that I find keeps views somewhat more readable. Note if you use the Sideview Editor to create and edit your views, it will follow these same conventions when it writes out the XML for you, so poking at a view with the Editor a little bit is a simple way to instantly "clean up" the whole view.
<module name="Search">
<param name="search"><![CDATA[
index=summary search_name="$query$" | timechart $function$(delay) as seconds span=$span$
]]></param>
<module name="ValueSetter">
<param name="arg.charting.legend.placement">none</param>
<param name="arg.charting.axisTitleX.visibility">collapsed</param>
<param name="arg.charting.axisY.minimumNumber">0</param>
<param name="arg.charting.axisY.maximumNumber">100</param>
<param name="arg.charting.axisLabelsY.majorUnit">20</param>
<param name="arg.charting.chartTitle">$query.Value$</param>
<param name="arg.charting.chart">column</param>
<module name="JSChart" layoutPanel="panel_row2_col1">
<module name="Search">
<param name="search"><![CDATA[
sourcetype=access_combined uri="*link?navSystem*" | timechart $function$(delay) as seconds span=$span$
]]></param>
<module name="ValueSetter">
<param name="arg.charting.chartTitle">$query.Value$</param>
<module name="JSChart" layoutPanel="panel_row2_col2"/>
</module>
</module>
</module>
</module>
</module>
Beyond that, you might want to look at the "template" param that all of the Sideview form element modules have. These allow you to have just $span$ in your search instead of span="$span$", where you have to worry about null token values creating malformed search syntax. The template param allow you to pull the foo= part up into the form element logic and this is a cleaner and simpler way to go.
... View more
