Developing Dashboards, Views, and Apps for Splunk Web

 


App.conf

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

App.conf

Configure app.conf to make your app visible to Splunk Web. If you're using app builder, it will configure this for you.

Configuration

To enable your app and make it in Splunk Web add the following stanza to $SPLUNK_HOME/etc/apps/<app_name>/default/app.conf:

[ui]
is_visible = true
label = <name>

add your app to the app launcher

Add the following stanza to app.conf to add your app into the app launcher. Fill out each attribute as described.

[launcher]
author=<author of app>
description=<textual description of app>
version=<version of app> 

Make sure you add an the following images to your app's ../appserver/static/ directory:

Update static content

Splunk's appserver caches all the static assets in your app (such as images, CSS and Javascript). If you release a new version of your app, you can set app.conf to make your updated assets available to users. Add the install stanza attribute to your app.conf file, and specify a build number. For example:

[install]
build = 2

If you want to reload your app's static content while you're working on the app and you don't want to clear your browser cache, hit this URI and click the button there:

http://localhost:8000/_bump

(Replace with your Splunk host:port.)

This documentation applies to the following versions of Splunk: 4.0 , 4.0.1 , 4.0.2 , 4.0.3 , 4.0.4 , 4.0.5 , 4.0.6 , 4.0.7 , 4.0.8 , 4.0.9 , 4.0.10 , 4.0.11 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.