Developing Dashboards, Views, and Apps for Splunk Web

 


Step 1: Create a dashboard

Step 1: Create a dashboard

There are several ways to create a Splunk dashboard:

All three of these options leverage Splunk's Simplified XML. Once you create a dashboard, you can always edit the Simplified XML upon which the dashboard is based.

Dashboard owners and permissions

Splunk dashboards are either private to a user, available to users of an app, or available to all users.

Splunk places private dashboards in the following location:

$SPLUNK_HOME/etc/users/<user>/<app>/local/data/ui/views/<dashboard_name.xml>

Splunk places dashboards available to users of an app (or available to all users) in the following location:

$SPLUNK_HOME/etc/<app>/local/data/ui/views/<dashboard_name.xml>

You can change the read and write permissions to a dashboard for users, based on their Splunk user roles.

Splunk Dashboard Editor

Use the Splunk Dashboard Editor to interactively create and edit dashboards. From the Dashboard Editor you add panels, create and edit searches for each panel, modify the visualizations representing the returned data, and specify permissions for the dashboard.

When using the Dashboard Editor, you do not have to edit any XML code. However, to enhance the dashboard you can always edit the Simplified XML upon which the dashboard is based.

To read more about the Dashboard Editor, see "Create and edit simple dashboards" and "Edit dashboard visualizations", both in the User Manual.

Use Splunk Manager to create a dashboard

You can create a dashboard directly from Splunk Manager.

1. Go to Manager > User interface > Views.

2. Click New and specify the following:

<?xml version='1.0' encoding='utf-8'?>
<dashboard>
  <label>Minimal Dashboard</label>
</dashboard>

3. (Optional) Modify permissions.

By default, the dashboard you create from Splunk Manager is private. In the Views page of Splunk manager, click Permissions for your dashboard to specify an app (or all apps) for the dashboard and to set permissions for users of the dashboard.

Create a dashboard from an XML file

You can create dashboards directly in an XML file and place the file in the appropriate directory in your Splunk installation. Use Simplified XML as described in this chapter. See "Dashboard owner and permissions" in this manual for the location of source dashboard files.

After copying the dashboard file to the appropriate directory, refresh Splunk as follows:

http://<Splunk Host>:<Splunk User Port>/info

OR

Splunk's Simplified XML syntax

Splunk's Simplified XML syntax allows you to create basic dashboards. The following sections of this chapter walk you through the steps of developing a dashboard using Simplified XML. However, here are some of the basics of Simplified XML:

Use the refresh attribute to set how frequently, in seconds, to refresh the dashboard. For example, <dashboard refresh="30"> sets the refresh rate to 30 seconds.
<event>: Displays a list of events.
<table>: Displays data in a table.
<chart>: Displays returned data in a chart. <option> tags define the type and layout of the chart.
<searchName>: specifies a saved search.
<searchString>: specifies an inline search specific to that panel.
<title>: Display name for the panel.
<earliestTime>, <latestTime>: specifies the time range for the search.
<option name="charting.chart"></option> defines the type of visualization, such as pie or radialGuage
<option name="count"></option> defines the number of rows to display.


See the Splunk Panel Reference for details on specifying visualizations for panels.

Use HTML entities for special characters

Simplified XML does not support the following five characters. Use HTML entities to display these characters:

Character HTML Entitiy
"
&quot;
'
&apos;
<
&lt;
>
&gt;
&
&amp;

This documentation applies to the following versions of Splunk: 4.3 , 4.3.1 , 4.3.2 View the Article History for its revisions.


You must be logged into splunk.com in order to post comments. Log in now.

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.

Feedback submitted, thanks!