Developing Dashboards, Views, and Apps for Splunk Web

 


How-To FAQ

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

How-To FAQ

Basic directions for the most commonly requested Splunk modifications that require developer work, rather than reconfiguration.


Rebrand the Splunk Web Interface

Use skins to modify Splunk's appearance with CSS.


Customize the Splunk Web Interface's Layout and Behavior

Use skins to modify Splunk's appearance and behavior with CSS.


Launch Splunk from Your Interface

Use permalinks to open Splunk and run specific searches encoded into each permalink's URL.


Search with Splunk from another application

Choose your API: command line (CLI) or SOAP.


Manage Splunk setting and users from another application

You can control Splunk through two APIs: command line (CLI) or SOAP.


Send Live Splunk alerts to another application

Set up an alert script - a shell script called with contextual parameters whenever a Live Splunk meets its alert threshold.


Preconfigure, customize or tune specific data inputs

Create a bundle with a shrinkwrapped input configuration and/or any properties, regular expressions, or Saved Splunks customized for your data.


Preload Saved and Live Splunks

Create a bundle with the Saved and Live Splunks you wish to install on your Splunk Server instances.


Add processing not available through configuration alone

Create a module that adds one or more new processors to your Splunk Server instances.


Access data not supported by Splunk's built-in input modules

Create a module that includes an input processor to access your data, and then passes it along to Splunk's universal pipeline or a custom pipeline of your own.

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!