Can you refer to $click.value$ inside the HTML in StaticContentSample

[coleman07]

I would like to use HTML via the StaticContentSample module to create a header for a graph based on clicking a previous graph. Is there a way to get the value of $click.value$ into the HTML in the StaticContentSample module?

<module name="ConvertToIntention">
...
...
   <module name="StaticContentSample">
     <param name="text"><!CDATA[
       <h1> Graph for $click.value$ </h1>
     </param>
   </module>

I am using the SimpleResultsHeader but the font size is not big enough. I probably could go in and create a custom CSS file and change the font for the result header.

Thanks for the help.

[sideview · Accepted solution]

No I'm afraid the StaticContentSample module does not do $foo$ substitution, so you cannot use it to include the value of $click.value$.

However, you can download Sideview Utils from the sideview site ( http://sideviewapps.com/apps/sideview-utils/ ), install it on your Splunk instance, and that will give you lots of new modules with much improved functionality.

1) In this particular case, it'll give you the HTML module, which does do $foo$ substitution. So if you use HTML and it's "html" param, instead of StaticContentSample and it's "text" param, it'll substitute the $click.value$ whenever a new element is clicked in the chart.

2) Also, it provides the Search module which can replace the HiddenSearch module, and to make a long story short the Search module means you don't have to think about or use "intentions" any more. I mention this as relevant because since you have an inline drilldown, where clicking on a graph shows results from a second drilldown graph, you are probably using a ConvertToIntention module there.

3) There's a third improvement that's probably a welcome improvement to your situation too. In addition to bringing in lots of new modules that offer improved functionality over equivalent core modules, most of the remaining core modules that you'll still use get patched. JSChart, FlashChart and SimpleResultsTable are no exception and those three modules get patched so that instead of using $click.value$ all the time, you can use $click.fields.myFieldName$, and $click.fields.myOtherFieldName$. There are even some other keys added to the output like $click.searchTerms$.

But there are actually a ton of other improvements, even just considering your situation here. These are just the top 3.

[sideview]

Well Sideview is tested in IE6 and IE7, but you might still be able to hit bugs that my testcases haven't found.

[coleman07]

Does Sideview work better in multiple browsers? I am finding that my dashboard is not reliable in IE or Chrome.

[coleman07]

I am definitly going to look at sideview!!