All Apps and Add-ons

sideview Redirector from a chart

timmalos
Communicator

Hi.

I got a static select:

<module name="StaticSelect" layoutPanel="mainSearchControls">
            <param name="settingToCreate">group_setting2</param>
            <param name="label">Summarized by: </param>
            <param name="searchWhenChanged">True</param>
            <param name="staticFieldsToDisplay">
                <list><param name="label">Port</param><param name="value">Port</param></list>
                <list><param name="label">Host Storage Domain</param><param name="value">HSD</param></list>
                <list><param name="label">Logical Unit</param><param name="value">LU</param></list>
            </param>    

After that I got an HiddenSearch:

<module name="HiddenSavedSearch" layoutPanel="panel_row1_col1" group="Title" autoRun="True">
    <param name="savedSearch">VSP_LU_Summary_IOPS_Top_TimeChart</param>
    <module name="ConvertToIntention">
         <param name="settingToConvert">group_setting2</param>
         <param name="intention">
             <param name="name">stringreplace</param>
             <param name="arg"><param name="summary"><param name="value">$target$</param></param> 
         </param>
         </param>                   
        ...
        <module name="HiddenChartFormatter">    
        ... 

All this works well, I got a $summarize$ variable in my savedSearch.
I want to add a redirector when an user click on the chart. I need to redirect to the correct view depending on the choice made by the user for $summarize$( LU or Host or HSD) and call the correct view $summarize$_Details.xml (LU_details, Host_Details.xml,HSD_Details.xml)

I tried this:

<module name="Redirector">
    <param name="url">$summary.label$_Details</param>
    <param name="arg.form.vsp">$vsp.label$</param>
    <param name="arg.form.$summary.label$">$click.value$</param>
</module>

But all variables are empty.
Thanks for your help,

sideview
SplunkTrust
SplunkTrust

you would have $summary.label$ if you were using a Sideview Pulldown module instead of the core Splunk StaticSelect, and all sorts of other useful keys. StaticSelect will just be giving you $group_setting2$ though - and not $summary$. "Summary" is actually an intention, and since you're already using Sideview Utils you don't want to be using that at all. The Sideview docs and workign examples - particularly on the page that introduces the Search module - will tell you more and then you'll be able to delete the ConvertToIntention module and never use it again.

But more generally if you're already using Sideview Utils then you really shouldn't be using StaticSelect or SearchSelectLister by the way - you should use Pulldown. Read the Pulldown docs and the docs about linking (ie Redirector) and things will get a lot simpler.

And don't use the $foo.label$ keys for under-the-hood stuff like drilldown arguments and url components. Use $foo$ or $foo.rawValue$. Again the docs and examples can explain.

0 Karma

sideview
SplunkTrust
SplunkTrust

OK. There's probably a lot of things that could be improved fwiw. There always are. If you have a second check out the Sideview Utils homepage which has a little gallery table that gives you some examples of problems and solutions. I say this only because most early users start only using one or two things because they don't know about the other 20 things. Cheers though. I understand the hesitation.

0 Karma

timmalos
Communicator

Ok thanks a lot for your answer. Fact is that I would avoir to use siddeview as I need it only for this case, I managed to make everything to work with intentions except this. I will try with $group_setting2$ if I can avoid the redirector module so that I can keep my core Splunk modules. If not then sideview is for me 🙂

0 Karma