Documentation > Splunk > Developing Dashboards, Views, and Apps for Splunk Web > Re-brand Splunk

Developing Dashboards, Views, and Apps for Splunk Web

 


Start Here
Command Line Interface
SOAP API
Bundles
Modules
Skins
Workflow Integration
Search Language
Built-In Processors

Re-brand Splunk

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

Contents

Re-brand Splunk

Use a custom skin and your own images to re-brand the Splunk interface for your organization. Create a new directory for your theme's images under $SPLUNK_HOME/share/splunk/search/images/skins and change the path and filenames in your css file.


Many images are constrained in size by other elements that are part of the default interface, outside the skin css file. For best results, use the same size image as the one you are replacing.


Examples

Put a new logo next the Splunk box on the home page by specifying another image. Change a#logo for the free version and .proVersion a#logo for Splunk Professional. 


a#logo {
        background-image:url(/images/skins/blue/logo_136x52.jpg); /* was basic/logo_splunk.png */
        background-repeat:no-repeat;
}

.proVersion a#logo {
        background-image:url(/images/skins/blue/logo_202x65.jpg); /* was basic/logo_splunk_pro.png */
        background-repeat:no-repeat;
        width:202px;
        height:65px;
}

Change the logo on the Splunk Professional login page: 


.proVersion a#bigLogo {
        background-image:url(/images/skins/blue/logo_blue.gif); /* was basic/logo_big_splunk_pro.png */
        background-repeat:no-repeat;
}
Retrieved from "http://docs.splunk.com/Documentation/Splunk/2.2.3/Developer/RebrandSplunk"

This documentation applies to the following versions of Splunk: 2.1 , 2.2 , 2.2.1 , 2.2.3 , 2.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!