Topics

| pdf version

Splunk > The IT Search Company

  • Search and navigate IT data from applications, servers and network devices in real-time.
  • Download Splunk

Localized Splunk documentation

Looking for Splunk documentation in other languages?

Developer manual overview

This documentation applies to the following versions of Splunk: 4.0 , 4.0.1 , 4.0.2 , 4.0.3 , 4.0.4 , 4.0.5 , 4.0.6

Developer manual overview

Welcome to the Splunk Developer manual. This manual contains instructions on developing for Splunk, from changing Splunk's appearance to extending the API. Primarily, this manual focuses on customizing Splunk's UI and building Apps.

What is an App?

At a high level, an App is a workspace that solves a specific use case for your company. For example, a single Splunk install can run a helpdesk App, a business analytics App, the Windows App and the Search App, all at the same time. Apps:

  • Focus on aspects of your data.
  • Are built around use cases.
  • Support diverse user groups and roles.
  • Run in tandem.
  • Contain any number of Splunk configurations and knowledge objects.
  • Are completely customizable, from front to back end.
  • Can include Web assets, such as HTML, CSS and JavaScript.

Why Apps?

Apps let you construct and maintain different environments on top of one Splunk instance. One Splunk installation can run multiple Apps. This way, any number of different groups can use the same Splunk instance without running into each other.

For example, you can make an App for all your helpdesk employees and a different App for your marketing department. When a user in the helpdesk role logs into Splunk, they'll see a customized environment that helps them track their support cases. When a user from the marketing group logs in, they'll see the business analytics App, where they can run reports on business trends and web activity. Meanwhile, the Splunk admin can maintain all the installed Apps, as well as build and install more.

By building Apps, you can create separate contexts for the different groups of Splunk users within your organization: one App for troubleshooting your email servers, one App for analyzing business trends, and so on. This way, everyone can use the same Splunk instance, but see only data that is relevant to their interests. Some groups can access multiple Apps while some may see only one. Apps are highly customizable, so you get to decide who sees what and how it works.

Who should use this?

This manual is for anyone who wants to make a change to Splunk Web, build a dashboard, a form search or an App, or extend Splunk via the REST API. Developing for Splunk is easy. You don't need to be a developer to build a Splunk App. It helps to be familiar with Splunk's configuration components, but you can pick up this knowledge throughout this manual. The App framework is straightforward enough that you should be able to quickly configure your Splunk installation to suit your use case.

Revision: 207 | Contact | Privacy Policy | Terms of Use | Community content licensed under Creative Commons