Documentation > Splunk > Developing Dashboards, Views, and Apps for Splunk Web > How Splunk Uses Skins

Developing Dashboards, Views, and Apps for Splunk Web

 


Overview
REST API
Configuration files
Splunk Web appearance

How Splunk Uses Skins

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

Contents

How Splunk Uses Skins

The default Splunk Web interface is defined by the HTML, CSS, JavaScript and XSL found under the $SPLUNK_HOME/share/splunk/search directory. Each skin has a CSS file that overrides the default styles for text color, background color, background image, and some other associated


Skins css Files 

$SPLUNK_HOME/share/splunk/search_oxiclean/static/css/skins

The .css files in this directory are where most customizations are done. If you put a file in this directory, it will appear in the Themes menu in Splunk Web. Since any file is assumed to be a skin, don't forget to remove temporary files created by your text editor. The standard skins provided are basic.css, the default theme, black.css, the all-black "inverted" or "night mode" theme, and desert.css, the neutral brown-toned theme. You can use any of these files as a base to design your own themes.


Images/skins directory 

$SPLUNK_HOME/share/splunk/search_oxiclean/images/skins

This is the standard location for image files, one directory for each skin. You can use the default images in your new skins by specifying their path from $SPLUNK_HOME/share/splunk/search_oxiclean (like background-image:url(/images/skins/basic/menu_arrow_bg.gif.) Put any new images in a new directory to avoid confusing them with the default ones.

Retrieved from "http://docs.splunk.com/Documentation/Splunk/3.2.3/Developer/HowSplunkUsesSkins"

This documentation applies to the following versions of Splunk: 3.2 , 3.2.1 , 3.2.2 , 3.2.3 , 3.2.4 , 3.2.5 , 3.2.6 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.

Feedback submitted, thanks!