Developing Dashboards, Views, and Apps for Splunk Web

 


Use App builder

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

Use App builder

Use App builder to create and customize your App workspace. You'll find App builder in Splunk Manager, in the Apps section. App builder provides a template to accelerate your App building process. In versions of Splunk prior to 4.0.5, there is only one template available -- sample_app.

sample_app

The sample_app template provides you with a Splunk App tutorial. This App is built on a small sample of sendmail data(located in $SPLUNK_HOME/etc/apps/sample_app/). In this template, you'll find:

Use App builder in Splunk Web

To use App builder in Splunk Web, follow these instructions:

1. Log in to Splunk Web and navigate to Splunk Manager (click the Manager link in the upper right-hand corner).

2. Click on Apps.

3. Hit the Create App... button to create a new App.

4. Enter a Name for your App. For example, helloworld. This name maps to the App's directory in $SPLUNK_HOME/etc/apps/.

5. Enter a Label for your App. This label maps to the label setting app.conf. Label and name can be the same, for example Hello world. The label also appears in the Splunk Web App drop-down (the upper left-hand corner of Splunk Web).

6. Pick the sample_app app template.

7. Add images, assets or files. For any files you don't specify, App builder uses the template's defaults. You can:

8. Save your App. You do not have to restart Splunk before your App is available, but you may need to restart to load configurations.

9. Continue building out your App by customizing your App's look and feel. Also, add configurations and knowledge objects.

This documentation applies to the following versions of Splunk: 4.0 , 4.0.1 , 4.0.2 , 4.0.3 , 4.0.4 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.