Like others, want to display a list of saved searches (like splunk 3.x did) on my dashboard. I have added the following xml snippet to my dashboard to attempt to do this:
` This lists all of the saved searches you have access to
<!-- Saved Searches --> <module name="EntityLinkLister" layoutPanel="panel_row1_col1"> <param name="entityPath">saved/searches</param> <param name="settingToCreate">savedSearchz</param> <param name="entityFieldsToDisplay"> <list> <param name="label">name</param> <param name="value">name</param> </list> </param> <module name="HiddenSearch" > <param name="search">| savedsearch "$savedSearch$"</param> <module name="ConvertToIntention"> <param name="intention"> <param name="name">stringreplace</param> <param name="arg"> <param name="savedSearch"> <param name="fillOnEmpty">True</param> <param name="value">$savedSearchz$</param> </param> </param> </param> <module name="ViewRedirector"> <param name="viewTarget">flashtimeline</param> </module> </module> </module> </module>
This displays one column with 30 of my saved searches. How do i increase the number per column and add more columns to the list?
1) running the search string itself instead of
| savedsearch $searchName$
I think that if you have the 'search' field as the value instead of the name,
<list> <param name="label">name</param> <param name="value">search</param> </list>
then you'll be able to avoid using the savedsearch command like so:
<module name="HiddenSearch" > <param name="search">$savedSearch$</param>
2) changing the number of saved searches displayed:
I think the EntityLinkLister just takes a
count param, which should work. But maybe you've tried that already.
3) Making more than just one column.
This is a lot harder, in that the automatic behaviour that 3.X had is no longer there and I think that's what you're asking about.
First, I assume you want it to look like the 'summary' view, in that you want three lists of blue links, but you want the second list to pick up right where the first one left off, and the third to continue from the second.
Frankly it's probably easier to just put a Paginator module above the EntityLinkLister (see how this is done in the search app's summary view), and have only a single column at a time.
However you can do it manually in the advanced XML using three nearly identical blocks of config. Assuming you want 30 rows in each of the 3 SearchLinkListers:
You can render the first into layoutPanel="panel_row1_col1_grp1", and give its search this on the end:
... | head 30
Then layoutPanel="panel_row1_col1_grp2" and the second one has this on the end:
... | head 60 | tail 30 | reverse
And then layoutPanel="panel_row1_col1_grp3", etc..
... | head 90 | tail 30 | reverse
( the reverse is needed because the tail comment reverses the order which we dont want here.)
Then you'll probably want a little 2-module combination of HiddenSearch and ViewRedirectorLink to give the user a 'see all' link below the three lists.
But again if it's acceptable to just throw a Paginator module in there and stick to a single column, that would take a lot less effort.
I haven't tried the entityLinkLister method you have here as it was not working when we needed it. We found a way to get all the searches in a list (ala 3.0) using a custom command (http://answers.splunk.com/questions/388). Obviously a lot more work than the entityLinkLister method but the target search is the actual search and not the savedsearch command which is quite helpful.
However it does not allow the result list to flow across multiple columns something we would really really like to see too!