Customization options
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Contents
Customization options
Building dashboard, form searches and other views in Splunk isn't the only way to customize the way the Splunk Web looks. There are more options, including:
- 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.
- Embed Splunk dashboard elements in third party software: build a report or a dashboard and then IFrame it into a different Web application. Requires some knowledge of HTML and Splunk's view system, as well as a customized login or SSO.
- Customize event display: change the way your events display in Splunk, for example build a Twitter like interface to display events in as they stream into Splunk in real time. Requires some knowledge of HTML, Splunk's view system and possibly JavaScript.
- Custom CSS: add custom CSS to your view, or your app. You can also overwrite the CSS for specific elements or modules in your view. Requires knowledge of CSS. We also recommend you use Firebug, or some other CSS inspector, to help CSS development.
- Translate Splunk: add a set of translations for your Splunk instance. Requires a PO editor, and it may be helpful to understand how to use a PO editor for translations.
Useful URIs for customization
If you've made changes to your app's static content while you're customizing Splunk Web, you'll probably want to reload that content for all the users of your app. Hit this URI:
http://localhost:8000/_bump
(Replace with your Splunk host and port.)
The _bump endpoint will clear out the Splunk-related cached items in all users' browsers so that your new static content loads.
This documentation applies to the following versions of Splunk: 4.1 , 4.1.1 , 4.1.2 , 4.1.3 , 4.1.4 , 4.1.5 , 4.1.6 , 4.1.7 , 4.1.8 View the Article History for its revisions.