Customization options
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Customization options
Building dashboards, form searches, and other views in Splunk aren't the only ways to customize Splunk Web. 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 events display in Splunk, for example build a Twitter-like interface to display events as they stream into Splunk in real time. Requires some knowledge of HTML, Splunk's view system, and possibly JavaScript.
- 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.
- Translate Splunk 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.
If you've made changes to an app's static content while customizing Splunk Web, you can reload that content for all the users of your app using this URI:
http://localhost:8000/_bump
The _bump endpoint clears out the Splunk-related cached items in client browsers, allowing new static content to load.
This documentation applies to the following versions of Splunk: 4.3 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.6 View the Article History for its revisions.