Databases Reference
In-Depth Information
3.
In the editor that appears next, the value of View name will actually be used
as the filename and URL, so it must not contain spaces or special characters.
Let's call it errors_user_form .
4.
The name in the menu comes from the label tag inside the dashboard's
XML. Let's change that to Errors User Form :
<label>Errors User Form</label>
5.
Save the new dashboard and click on Open next to the dashboard.
6.
Next, convert all of the searches to inline using Edit | Edit search | Edit
as inline search , as we did in the previous example.
7.
Change <dashboard> to <form> and add the same <fieldset> block
as before.
8.
Insert user="$user$" into each <searchString> tag appropriately.
The XML in the end will be much larger than what we saw before, but hopefully
still understandable. Lines changed manually are highlighted in the following
code snippet:
<?xml version='1.0' encoding='utf-8'?>
<form>
<label>Errors User Form</label>
<fieldset>
<input type="text" token="user">
<label>User</label>
</input>
</fieldset>
<row>
<chart>
<searchString>
sourcetype="impl_splunk_gen" loglevel=error user="$user$"
| timechart count as "Error count" by network
 
Search WWH ::




Custom Search