Developing Views and Apps for Splunk Web

Customization options

• Customize the login screen Add a custom greeting to the login screen, letting users know important information about this Splunk instance. Requires minimal knowledge of HTML.

• Customize CSS Add custom CSS to a view or app. You can also overwrite the CSS for specific elements or modules in a view. Requires knowledge of CSS. We also recommend you use Firebug, or some other CSS inspector when working with CSS development.

• UI internationalization Add a set of localizations for a Splunk instance. Requires a PO editor, and it may be helpful to understand how to use a PO editor for translations.

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:

  http://<host:mport>/<locale_string>/_bump

As an example, you can use

http://localhost:8000/en-US/_bump

• debug/refresh:

  http://<host:mport>/debug/refresh

• Restart splunkd. For more information, see Start and stop Splunk Enterprise in the Admin Manual.

• 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 in the Admin Manual.