Splunk® Enterprise

Developing Views and Apps for Splunk Web

Download manual as PDF

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

Customization options and caching

Options for customization

There are several styling, behavior, and text customization options available for different components of the Splunk platform.

To learn about See
Adding plain or formatted text to the login page Customize the login page

Using CSS or JavaScript files to

  • Customize individual dashboards
  • Customize all dashboards in an app
Customize dashboard styling and behavior
Configuring UI internationalization UI internationalization
Adding HTML or images to a dashboard The <html> Simple XML element reference in Dashboards and Visualizations
Customizing integrated PDFs "Additional configuration options for integrated PDF generation" in the Reporting Manual

Clear client and server assets caches after customization

Static assets for apps are cached on the client and server side. If you update an item in the /appserver/static directory, you can see changes by clearing both the client and server caches. Clear the browser cache to update the client side. To clear the server cache, use one of the following options:

  • _bump:
As an example, you can use
  • debug/refresh:
  • Set cacheEntriesLimit=0 in web.conf. This setting is recommended only for development use cases and not for production. For more information, see the web.conf spec file in the Admin Manual.
Developer resources
Customize the login page

This documentation applies to the following versions of Splunk® Enterprise: 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.3.14, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11


Minor typo. In section "Clear client and server assets caches after customization", first bullet point:


The key "mport" should be "port", i.e. plain Splunk web port, as reflected by the example.

January 7, 2016

Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

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

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters