Developing Dashboards, Views, and Apps for Splunk Web

 


View reference material

Module reference

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

Contents

Module reference

Nav

AccountBar

(extends Splunk.Module) The bar at the top of most views, that contains the logo, says logged in as <user>, and contains the logout and admin links.

required params

(none)

optional params

AppBar

(extends Splunk.Module) This is the bar second from the top in most views. It contains the top level view categories (by default Dashboards Views Saved Searches), and the auxiliary links section (help | preferences | about).

required params

(none)

optional params

(none)

BreadCrumb

(extends Splunk.Module) Simple navigation breadcrumb for a multi-view flow.

required params

(none)

optional params

ManagerBar

(extends Splunk.Module) This is a header bar that shows up at the top of the view. Used specifically in Splunk Manager. When present in any view, it will display a header of "Manager: <view name>".

required params

(none)

optional params

(none)

TitleBar

(extends Splunk.Module) Control menu/actions menu. This module is persistent, and contains information such as the name of the dashboard, the name of the view, or the name of the view and associated saved search. The titlebar functions as a place for contextual actions, like saving a new search that has been run after loading a view.

required params

(none)

optional params

Messaging

GenericHeader

(extends Splunk.Module) This simple module just displays the configured text as a header element on the page.

required params

optional params

(none)

Message

(extends DispatchingModule) This module can display all messages to the user, or can be configured to display just a certain class of messages. Messages might come from searches, from alerts firing, from misconfiguration on the backend, from information about indexing status etc. The simplest configuration is a single Message instance with filter set to '*' -- meaning it will display all the messages broadcast. However, you can use multiple Message modules with different 'filter' params displayed in separate layout panels throughout a view. Messages are passed with a defined class, such as splunk.search.error. So if you have two Message instances, one configured with a filter of '*', and another with a filter of splunk.search, the latter will receive the splunk.search.error events, and the "*" instance will not. However when an unexpected message is passed down with the class of splunk.indexing.warn, the splunk.search instance will not display it but the the '*' instance will.

required params

optional params

Search

ExtendedFieldSearch

(extends FieldSearch) The basis for the form elements that add or remove intentions.

required params

optional params

FieldPicker

(extends HiddenFieldPicker) This module launches the field picker, a list of all available fields from which a user can select the fields to display. Descendants of this module that display events and summary information will pick up the field list specified or chosen here.

required params

optional params

FieldSearch

(extends Splunk.Module) Restrict searches to a specific field. Use this module to configure a form search with only one form field. To configure form searches with multiple forms, use ExtendedFieldSearch.

required params

optional params

HiddenFieldPicker

(extends DispatchingModule) This module implements an invisible control that hardwires which fields the user will see and what order those fields are in. When they are descendants of this module, other modules that display events and summary information will pick up the field list specified or chosen here.

required params

(none)

optional params

HiddenIntention

(extends Splunk.Module) Adds the given intention to any search it receives from upstream modules. There are several kinds of intentions, 'addterm', 'negateterm', 'stringreplace', and 'plot' are the main ones. A complete reference is beyond the scope of this description but one will hopefully be added to the documentation soon.

required params

optional params

(none)

HiddenPostProcess

(extends DispatchingModule) Adds a post-process search into the data tree. For more information on this module and how to set up a post process search, see How to use one search for a dashboard.

required params

optional params

(none)

HiddenSavedSearch

(extends Splunk.Module) Given a saved search name, either finds the last run search for that saved search or runs a new search depending on its configuration.

required params

optional params

HiddenSearch

(extends Splunk.Module) Runs a search behind the scenes. Passes results on to any children. You must set autoRun to true so that the search actually runs.

required params

(none)

optional params

PostProcessBar

(extends FieldSearch) This module lets you add a post-process search on any results you have returned. It doesnt re-run any search, but it will use that search language to do post-processing filtering on the results data.

required params

(none)

optional params

RadioButtonSearch

(extends FieldSearch) This module creates a set of radio buttons with submit and cancel buttons.

required params

optional params

SearchBar

(extends FieldSearch) This module creates a search bar with submit and cancel buttons.

required params

(none)

optional params

SubmitButton

(extends Splunk.Module) Creates a submit button that collects changes from its parent modules, and runs them when the user clicks the button.

required params

(none)

optional params

TimeRangePicker

(extends Splunk.Module) This module creates a drop-down menu that users can use to change the timerange. Timerange values and labels are pulled from the configuration in times.conf.

required params

(none)

optional params

ViewRedirector

(extends Splunk.Module) This module takes the context and settings information provided by its ancestors, dispatches the search and redirects the user to see that search in the specified view. When ViewRedirector receives a new context, and onContextChange() is called, it WILL REDIRECT to the specified view.

required params

optional params

ViewRedirectorLink

(extends ViewRedirector) This module puts a link in the view with the given label. When clicked it will take the context information provided by its ancestors, dispatch the search and redirects the user to see that search in the specified view.

required params

optional params

Results

AddTotals

(extends DispatchingModule) This module contains a checkbox that toggles whether or not results are previewable.

required params

(none)

optional params

Count

(extends DispatchingModule) This module allows the user to determine the number of events that should be displayed at a time. When used in conjunction with a Paginator module, the Paginator should be a descendent of the Count module, not an ancestor.

required params

optional params

DataOverlay

(extends DispatchingModule) This module allows the user to determine the data overlay mode for results

required params

(none)

optional params

EnablePreview

(extends DispatchingModule) This module contains a checkbox that toggles whether or not results are previewable.

required params

(none)

optional params

EventsViewer

(extends AbstractPagedModule) The EventsViewer module displays events resulting from the search that it's ancestor modules combined to specify. This module is very similar to SimpleEventsViewer, and one of these two modules will in the future be folded into the other.

required params

(none)

optional params

FlashTimeline

(extends FlashWrapper) This module contains a Flash object that is capable of displaying a chart of number of events over time. This chart will be updated asynchronously while the search is running.

required params

optional params

FlashWrapper

(extends DispatchingModule) This is the base class for all Flash modules. Unlike FlashChart and FlashTimeline, this simple module makes no assumptions about the swf it is asked to load.

required params

optional params

FieldViewer

(extends AbstractPagedModule) This simple module shows the top N values for a given field, along with a number in parentheses showing the number of events that had the given value.

required params

optional params

MaxLines

(extends DispatchingModule) This module creates a control that allows the user to set the maximum number of lines to display per event. Events truncated by this setting will generally be abstracted such that the most relevant lines are displayed. (refer to docs around the 'truncation_mode' arg to the events endpoint)

required params

optional params

MultiFieldViewer

(extends AbstractPagedModule) This module is typically for use within the sidebar, and shows a set of field names, with distinct counts next to them in parentheses. When the user clicks on the field names, a popup layer will open showing the top 10 values for that field. Clicking then on one of those values will add the proper field=value term and re run the search.

required params

(none)

optional params

NullModule

(extends Splunk.Module) This is just a null module, used when we need a placeholder. Takes up no space and tries to remain inconspicuous.

required params

(none)

optional params

(none)

Paginator

(extends DispatchingModule) This module displays a series of links to page around in your data. It must be configured to page either through the 'events' or the 'results' of your search.

required params

optional params

ResultsActionButtons

(extends Splunk.Module) Implements a set of buttons with which the user can save, print, export and share the results of their search or report.

required params

(none)

optional params

ResultsHeader

(extends SimpleResultsHeader) This module displays a header like '23,420 events' and is for placement generally above a FlashTimeline or above a set of modules implementing paging controls

required params

optional params

RowNumbers

(extends DispatchingModule) This module allows the user to determine if row numbering is enabled/disabled

required params

(none)

optional params

SearchTextSetting

(extends TextSetting) A search text input field that passes its contents down to its children as part of the settings map, styled to have a mag glass icon.

required params

optional params

Segmentation

(extends DispatchingModule) This module allows the user to determine the segmentation type to be displayed for events.

required params

optional params

Selector

(extends Splunk.Module) Creates a selction list from a set of options. Options can either be configured manually or by defining an entity endpoint from which to generate its options.

required params

optional params

SoftWrap

(extends DispatchingModule) This module contains a checkbox that toggles whether or not events are soft-wrapped. When off, event text will break in the page only where there is a linebreak in the actual data, and scrollbars will appear as necessary. When on, the event text will also break at the edge of the window.

required params

(none)

optional params

Sorter

(extends Splunk.Module) Sorter displays a list of fields that can be sorted upon. Given a list of field names, Sorter will create a set of delimited links which the user can click on. Clicking on these links will pass a "sort" setting down to Sorter's child modules which can iterpret how to preform the sort on their own.

required params

(none)

optional params

ShowSource

(extends DispatchingModule) This module waits for the search to complete and then renders a single field from the first row of the results

required params

(none)

optional params

(none)

SimpleResultsHeader

(extends DispatchingModule) This module displays a header like '23,420 events' and is for placement generally above a FlashTimeline or above a set of modules implementing paging controls

required params

optional params

(none)

SimpleResultsTable

(extends AbstractPagedModule) this module waits for the search to complete, and then renders its final results in a tabular format.

required params

(none)

optional params

SingleFieldChooser

(extends BaseReportBuilderField) This module contains a pulldown that allows you to select the field that you wish to use on the y-axis. This is generally used in conjunction with StatChooser which specifies the aggregator function for this field chosen here. Eg. if this module is set to 'kbps', and StatChooser is set to 'max', then the overall y-axis value will be max(kbps)

required params

(none)

optional params

(none)

SingleValue

(extends DispatchingModule) This module waits for the search to complete and then renders a single field from the first row of the results

required params

(none)

optional params

StaticRadio

(extends AbstractStaticFormElement)

required params

optional params

StaticSelect

(extends AbstractStaticFormElement)

required params

optional params

SuggestedFieldViewer

(extends MultiFieldViewer) This module shows fields that are not selected by FieldPicker (and thus not displayed in MultiFieldViewer or other modules) but which look like they might be interesting to the user.

required params

(none)

optional params

TextSetting

(extends AbstractFormSettingModule) A text input field that passes its contents down to its children as part of the settings map.

required params

optional params

Charting

AxisScaleFormatter

(extends BaseChartFormatter) This module contains a pulldown that allows you to choose whether you want the y-axis scale to be scaled logarithmically or linearly. When any other module has set the 'stacked' option, any log scaling becomes meaningless and so this module will both become invisible and revert to 'linear'.

required params

(none)

optional params

BaseChartFormatter

(extends Splunk.Module) this is an abstract base class for other chart formatting modules. This module should never itself be configured within a view.

required params

(none)

optional params

(none)

ChartTitleFormatter

(extends BaseChartFormatter) This module contains a text field that you can use to set the overall title of your chart.

required params

(none)

optional params

ChartTypeFormatter

(extends BaseChartFormatter) this module contains a pulldown that you can use to change between 'column', 'line', 'area' and various other chart types.

required params

(none)

optional params

FancyChartTypeFormatter

(extends ChartTypeFormatter) this module contains a styled pulldown that you can use to change between 'column', 'line', 'area' and various other chart types.

required params

(none)

optional params

FlashChart

(extends FlashWrapper) This module contains a Flash object that is capable of charting almost any search results that the Splunk backend can generate.

required params

(none)

optional params

HiddenChartFormatter

(extends Splunk.Module) this module contains a pulldown that you can use to change between 'column', 'line', 'area' and various other chart types.

required params

(none)

optional params

LegendFormatter

(extends BaseChartFormatter) this module contains a pulldown that you can use to change how the chart legend is displayed relative to the chart itself.

required params

(none)

optional params

LineMarkerFormatter

(extends BaseChartFormatter)

required params

(none)

optional params

NullValueFormatter

(extends BaseChartFormatter) This module contains a pulldown that controls how 'line' and 'area' charts should behave when there are gaps in the data. You can either treat null values as '0', leave an explicit gap, or interpolate between the values.

required params

(none)

optional params

SplitModeFormatter

(extends BaseChartFormatter) This module contains a pulldown that indicates whether or not to show multi-series data on a single combined plot vs. a separate plot for every series. For example, a search like "search error | timechart count by host" would render a separate chart for every "host" found.

required params

(none)

optional params

StackModeFormatter

(extends BaseChartFormatter) This module contains a pulldown that can be used to make bar and area charts display in 'stacked' mode. When the chart type is set to a value other than 'area' or 'column', this module becomes invisible and turns off the stacked mode if it was on.

required params

(none)

optional params

XAxisTitleFormatter

(extends BaseChartFormatter) this module contains a text field that you can use to change the title for the x-axis of your chart.

required params

(none)

optional params

YAxisRangeMaximumFormatter

(extends BaseChartFormatter) this module contains a text field that takes an integer, that determines the maximum y-axis value that should be displayed.

required params

(none)

optional params

YAxisRangeMinimumFormatter

(extends BaseChartFormatter) This module contains a text field that takes an integer, that determines the minimum y-axis value that should be displayed.

required params

(none)

optional params

YAxisTitleFormatter

(extends BaseChartFormatter) this module contains a text field that you can use to change the title for the y-axis of your chart.

required params

(none)

optional params

Converters

ConvertToDrilldownSearch

(extends Splunk.Module) EXPERIMENTAL.

required params

(none)

optional params

ConvertToIntention

(extends Splunk.Module) Converts a setting value to an intention, which it adds to its context and passes to its children.

required params

optional params

ConvertToRedirect

(extends Splunk.Module)

required params

optional params

(none)

Include

AjaxInclude

(extends Splunk.Module) EXPERIMENTAL. A simple wrapper for integrating external content via XMLHTTPRequest within the module framework. Note this is limited to same domain constraints. Emulates iframe like behavior (page is not refreshed on clicks) and binds an ajaxForm handler to all forms.

required params

optional params


IFrameInclude

(extends Splunk.Module) This simple module uses an inline frame (iframe) to show content from another URL.

required params

optional params

ServerSideInclude

(extends Splunk.Module) This module supports the concept of server side includes for custom content. Additionally, the Mako (see: http://www.makotemplates.org/) template language is supported.

required params

optional params

(none)

Lister

How to use lister modules.

EntityLinkLister

(extends AbstractEntityLister)

required params

optional params

EntityRadioLister

(extends AbstractEntityLister)

required params

optional params

EntitySelectLister

(extends AbstractEntityLister)

required params

optional params

LinkList

(extends DispatchingModule) DEPRECATED. This module is no longer supported, and should be replaced with one of the *Lister modules in the /lists subdirectory.

required params

optional params

SearchLinkLister

(extends AbstractSearchLister)

required params

(none)

optional params

SearchRadioLister

(extends AbstractSearchLister)

required params

optional params

SearchSelectLister

(extends AbstractSearchLister)

required params

(none)

optional params

Switchers

Switchers are another way to create tabs or pulldown elements that users can use to switch out content or ui controls underneath. They may seem similar to the 'lister' modules but they are qualitatively different. Switchers create a fork between arbitrarily different config branches underneath, but the choice doesnt influence any individual search in those child branches. And listers on the other hand allow the user to insert input that effects the search(es) underneath, but they do not switch one set of modules out and replace it with another set of modules.

The current Switcher classes are 'PulldownSwitcher', 'TabSwitcher', 'LinkSwitcher', and 'ButtonSwitcher'. ('ButtonSwitcher' is a little misnamed in that it actually presents little square icons. Because you'd need to create custom images for Buttonswitcher, and because also it's a little special cased for it's usage within flashtimeline you probably should start with the other 3.) And technically there is another switcher called 'ShowHideHeader' but i'll cover him someday seperately cause you use him in different circumstances.

How to use switcher modules.

ButtonSwitcher

(extends TabSwitcher) This is a subclass of AbstractSwitcher, and when configured to have N children (and thus N subtrees of descendant modules), it will display the a button for each child. The button style is determined by a class set on the group name. When the user clicks a different button, the corresponding child and its descendant modules will be shown on screen and all other child modules (and descendants thereof) will be hidden.

required params

optional params

ConditionalSwitcher

(extends TabSwitcher) This is a subclass of AbstractSwitcher. When the given condition is true, it will display the first child tree. When false it will display the second child tree.

required params

optional params

LinkSwitcher

Example here: LinkSwitcher

(extends TabSwitcher) This is a subclass of AbstractSwitcher, and when configured to have N children (and thus N subtrees of descendant modules), it will display the a link for each child. When the user clicks a different link, the corresponding child and its descendant modules will be shown on screen and all other child modules (and descendants thereof) will be hidden.

required params

optional params

PulldownSwitcher

(extends AbstractSwitcher) Creates a pull-down menu populated with results from its children. Shows one set of child modules at a time. Children can be serialized -- they pass results on -- or independent.

required params

optional params

TabSwitcher

(extends AbstractSwitcher) This is a subclass of AbstractSwitcher, and when configured to have N children (and thus N subtrees of descendant modules), it will display the 'group' params of those modules in a set of tabs. Like PulldownSwitcher, this module shows only one child at a time. Displays the results of its child modules in a set of tabs. When the user clicks a different tab, the corresponding child and its descendant modules are shown on screen and all other child modules (and descendants thereof) are hidden.

required params

optional params

ShowHideHeader

(extends AbstractSwitcher) This is a somewhat restrictive switcher class, in that it should only ever have two children, and the second child tree should be either a null module, or in theory some short text like '(click the link above to show formatting options)'

required params

optional params

Internal modules

You probably won't ever use these.

Jobs

JobManager

(extends Splunk.Module) This large module dominates the page and is intended to supply management functionality for many previously dispatched searches.

required params

optional params

JobStatus

(extends DispatchingModule) This module is intended to supply basic search management functionality and information/general status information.

required params

(none)

optional params

Report builder

BaseReportBuilderField

(extends Splunk.Module) This is the abstract base class of all of the report_builder modules that effect the underlying search.

required params

(none)

optional params

(none)

ReportBuilderSearchField

(extends BaseReportBuilderField) this is a class for report builder, that has significantly more complex behaviour than SearchField, and is useful only in the report_builder view

required params

(none)

optional params

(none)

ReportSubType

(extends BaseReportBuilderField) This module contains a pulldown that allows you to split 'trend over time' and 'correlation' searches by a single field, split them by multiple series, or not split them at all.

required params

(none)

optional params

(none)

ReportType

(extends BaseReportBuilderField) This module contains a pulldown that allows you to select the general type of report that you are trying to build. Examples of its options are 'trend over time', 'correlation', 'top values of a given field' etc..

required params

(none)

optional params

(none)

SplitByChooser

(extends BaseReportBuilderField) This module contains a pulldown that allows you to select the field that you wish to split by, when doing a 'trend over time' or 'correlation' search, and when youve chosen to split by a single field.

required params

(none)

optional params

(none)

StatChooser

(extends BaseReportBuilderField) This module contains a pulldown that allows you to select the aggregator function that you wish to apply to your y-axis field. Its options include functions like 'sum', 'average', 'count' and 'distinct count', .

required params

(none)

optional params

(none)

TimeRangeBinning

(extends BaseReportBuilderField) This module contains a text field and a pulldown, that together the user can use to set the size of buckets in 'trend over time' searches. The first field takes an integer, and the pulldown contains options of 'month, day, hour, minute, second'

required params

(none)

optional params

(none)

Base class

Splunk.Module

This is the abstract base class for all modules.

required params

(none)

optional params

(none)

DispatchingModule

(extends Splunk.Module) This is the abstract base class for all modules that can only work with dispatched searches. In a nutshell all modules inheriting from this module will have all the functionality needed to display data from asynchronous searches. When a parent module tries to pass along a search to one of these modules, that search will be dispatched beforehand. As such, the code within dispatching module classes always assumes that the search has already started running.

required params

(none)

optional params

(none)

This documentation applies to the following versions of Splunk: 4.1 , 4.1.1 , 4.1.2 , 4.1.3 , 4.1.4 , 4.1.5 , 4.1.6 , 4.1.7 , 4.1.8 View the Article History for its revisions.


Comments

Errors in documentation for HiddenSavedSearch. Should read "The default useHistory method is Auto". Also, the parameter useHistory=None is not documented.

Tradel2
October 15, 2010

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!