Simple XML Reference

You can use Simple XML source code to build dashboards and forms. Use the dashboard source code editor to access and edit Simple XML. In some cases, Simple XML provides customization options not available in the dashboard user interface editor.

Overview

Elements

Simple XML source code has parent and child elements, starting with a <dashboard> or <form> root element. Use elements to structure a dashboard or form. For example, you can use a <row> element to organize one or more <panel> child
elements in a dashboard. A <panel> can contain visualization elements such as a <table> or a <map>.

Attributes and options

Most Simple XML elements have attributes and options that you can use to configure dashboard appearance and behavior.

In visualization elements, you can use options to configure formatting, interactivity, and other components, such as legend placement or the colors to use in a chart.

Attributes and options have types, like number or text. Some attributes and options have default settings and additional requirements, such as an accepted value range.

Using the Simple XML Reference

Get reference information about Simple XML elements for building dashboards and forms.

Attributes

Use the following attributes to configure <dashboard> and <form> root elements.

Name

Type

Default

Description

hideChrome

boolean

false

Hide the Splunk bar, app bar, and footer.

For this and all of the following hide<element_name> attributes, if they are specified as a URL query string parameter without a value, they are handled as "true". For example, both of the following query strings are handled as "true".

<dashboard_url>?hideChrome

<dashboard_url>?hideChrome="true"

hideAppBar

boolean

false

Hide the bar listing available apps.

hideEdit

boolean

false

Hide the dashboard editing interface. If enabled, use the Settings > User interface > Views or the Dashboards page to edit the dashboard.

input (form)

Input elements define the user interaction interface for a form. Selection elements, such as radio buttons or a checkbox, let users click or select choices. You can use a search to populate selection elements dynamically. Other inputs, such as time or text, let users type content or change a search time range.

Use attributes to configure user inputs and use child elements to define input content. Some child elements are shared across several input types. Others are specific to the input type.

Input attributes

Use these attributes in any form input.

Name

Type

Description

depends

Comma-separated list

All tokens in the list must be defined for the input to render. These tokens might be used in an input or drilldown context in the form.

id

Text (minimum two characters)

Input identifier.

Only alphanumeric and underscore characters are valid. The id cannot begin with a number or the underscore character.

rejects

Comma-separated list

Prevent input rendering if one or more tokens in this list are defined. These tokens might be used in an input or drilldown context in the form.

searchWhenChanged

Boolean

Specifies to run the search when the selection changes. Defaults to false.

token

Token name

Token representing the user selected value from this input.

type

One of the following input types.

checkbox

dropdown

link

multiselect

radio

text

time

Shared input child elements

Use these child elements in <input> elements. There are a few usage exceptions.

Default value for the input. If the user does not select or input a value, this value is used. Overrides the initialValue.

<earliest> and <latest>

The earliest and latest times defining the <search> time range. Use relative time modifiers, as described in Specify time modifiers in your search , or use UNIX epoch time format for absolute time.

Not available for text or time inputs.

<fieldForLabel> and <fieldForValue>

In dynamically populated selection inputs, these elements indicate the search result fields to use for the label and value of each choice. Use with the <search> element that generates results for populating the input choices.

Not available for text or time inputs.

<initialValue>

Initial value for the input. This value is used before the user selects or inputs a value.

<label>

Label for the input.

<prefix>

Prefix to prepend to the selected value. For example, you can add a quotation mark to the beginning of a string value and use <suffix> to add a closing quotation mark after the string value. The prefix can be a string or regular expression.

<search>

Search that dynamically populates choices for the input. Use the ref attribute of the <search> element to reference a search from a report. See <search>.

Not available in text inputs.

<suffix>

Suffix to append to the selected value. The suffix can be a string or regular expression.

checkbox child elements

A string that will be placed between each selected value. Typically, you specify " OR " or " AND " using upper case – do not specify the quote marks, but specify a space character before and after the text.

<valuePrefix>

text

String prefixed to the value of the input element. Can be a regular expression.

<valueSuffix>

text

String appended to the value of the input element. Can be a regular expression.

multiselect child elements

If true, enables the selection of custom values typed into the text field for the input.

<delimiter>

text

A string that will be placed between each selected value. Typically, you specify " OR " or " AND " using upper case – do not specify the quote marks, but specify a space character before and after the text.

<valuePrefix>

text

String prefixed to the value of the input element. Can be a regular expression.

<valueSuffix>

text

String appended to the value of the input element. Can be a regular expression.

text child elements

time child elements

change (form input)

Use a <change> element to define how a form responds to user input. When a user makes a selection or types in an input, the actions configured in the <change> element for that input happen.

The <change> element is available in the following <input> types.

<checkbox>

<dropdown>

<radio>

<text>

<time>

Use tokens to define responses to user input
Inside a <change> element, you can define actions such as token setting or other token updates that help you manage dynamic behavior or display in the form.

Conditional responses
Use one or more <condition> elements inside a <change> element to define conditional responses to specific user input. See <condition> for more information.

row

A row contains one or more <panel> child elements in a dashboard or form. Use a row to configure panel grouping and layout.

Attributes

Use the following attributes within the <row> element.

Name

Type

Default

Description

depends

Comma-separatedlist of tokens

All tokens from the list of tokens must be defined to render this row in a dashboard.

rejects

Comma-separatedlist of tokens

All tokens from this list must be defined to prevent this row from rendering in a dashboard.

id

text

Row identifier.

Only alphanumeric and underscore characters are valid. The id cannot begin with a number or the underscore character.

The following terms are reserved for internal use and cannot be used for an id.

dashboard

search

default

submitted

footer

url

header

Child element

A <row> contains one or more <panel> elements.

panel

Inside a <row>, use a <panel> to contain one or more visualizations. You can use panels to manage visualization grouping and layout. You can also show or hide panels dynamically.

Panel alignment
Two or more visualization elements in a panel align vertically, except for single value visualizations. Two or more single value visualizations in the same panel are grouped horizontally.

Using visualization attributes and options

Like other Simple XML elements, visualizations use attributes for identification and for managing display. There are several shared attributes that you can use in any visualization type. Some visualizations have additional attributes available.

Each visualization has several available <option> named properties for configuration. Shared options can be used in all visualizations. Other <option> properties are specific to one visualization type.

Option syntax
Use the following option tagging syntax within the visualization element.

<option name="[option_name]">[option_value]</option>

For example, use the following option to show the Export button in a panel.

<option name="link.exportResults.visible">true</option>

Shared attributes

Use the following attributes to identify and control display for any visualization element.

Name

Type

Description

depends

Comma-separated list of tokens that must be set for the panel, row, or visualization to display.

All tokens from the list of tokens must be defined to render this visualization.

For example, <chart depends="$show1$"> indicates that the chart is shown only when the $show1$ token is set.

rejects

Comma-separated list of tokens that must be set for this visualization to be hidden.

All tokens from this list must be defined to prevent this visualization from rendering.

For example, <table rejects="$one$, $two$"> indicates that the table is hidden when either the $one$ or $two$ token is set.

id

text

Visualization identifier.

Only alphanumeric and underscore characters are valid. The id cannot begin with a number or the underscore character.

The following terms are reserved for internal use and cannot be used for an id.

Column formatting

You can use color and other formatting in table columns to show context or highlight values. Table column formatting uses a different syntax from other visualization options. To learn about formatting table columns in Simple XML, see Table column Simple XML.

Example
Example of a table panel using an inline search, displaying five rows, and disabling row numbers:

Table sparklines

Table sparklines show recent behavior patterns for each table row. You can format a sparkline in Simple XML.

Single value sparklines work differently from table sparklines. See single value for more details.

Configuring sparkline formatting in Simple XML does not change sparkline appearance in PDF. Sparklines appear without additional formatting in PDF.

Generating a sparkline

To use the formatting options described here, your search must generate a sparkline in the visualization. To create a sparkline, use the chart or stats command sparkline( ) function. See Add sparklines to search results in the Search Manual for more details.

Format syntax and attributes
The <format> element contains formatting rules for sparklines. Include the "sparkline" type attribute and the field that the sparkline is tracking.

chart

Use the <chart> element to add column, bar, line, area, bubble, or scatter charts to a <panel>. You can also use the <chart> element to add a gauge visualization to a <panel>.

The search generating a chart can be an inline search or a saved report. A saved report can contain chart format settings. These settings are used by default, but you can use options and and attributes in your Simple XML source code to override them.

map

Use the <map> element to add a Choropleth or cluster map to a <panel>.

Attributes

In addition to the shared attributes for visualizations, you can use the following attributes in a <map> element.

General map options

In addition to the shared options for visualizations, you can use the following options to configure Choropleth and cluster maps.

Name

Type

Default

Description

drilldown

all | none

all

Use all to enable drilldown or none to disable drilldown.

mapping.fieldColors

One or more <field> : <color_hexvalue> mappings.

A comma-separated list of field names mapped to hexadecimal color values (0xRRGGBB) to define colors for specific series.

mapping.map.center

(lat,long)

The initial center point of the map. Latitude values can range from -85 to 85, with values outside of this range being clipped. Longitude values can range from -180 to 180, with values outside of this range being wrapped to fall within it.

mapping.map.scrollZoom

Boolean

false

Indicates whether the map zooms when a user scrolls the map.

mapping.map.panning

Boolean

true

Indicates whether the map pans when dragged.

mapping.map.zoom

Number

2

The initial zoom level of the map.

mapping.map.fitBounds

(south-lat,west-long,north-lat,east-long)

The initial bounds to fit within the map view area. Latitude values can range from -85 to 85, with values outside of this range being clipped.

Longitude values can range from -180 to 180, with values outside of this range being wrapped to fall within it.

Values assigned to this property effectively override any values assigned to the center or zoom properties.

mapping.seriesColors

List

Default*

Comma-separated list of hexadecimal color values (0xRRGGBB). The list indicates sampling colors for series with no specific fieldColors color assigned to them.

mapping.showTiles

boolean

true

Specify whether to show or hide map tiles.

mapping.tileLayer.tileOpacity

text

1

Specifies the opacity of the tiles. Values can range from 0 (transparent) to 1 (opaque).

mapping.tileLayer.url

URL template

See description

The URL to use for requesting tiles, based on the following template.

http://(s).tile.openstreetmap.org/(z)/(x)/(y).png

mapping.tileLayer.subdomains

[string,. . .]

[a,b,c]

List of subdomains over which to distribute tile requests. More subdomains allows more tiles to be requested simultaneously.

Use a string array to specify any number of hex color values. List the colors in an order corresponding to rangeValues values. The hex value format should be either 0xFFFFFF or FFFFFF.

If there are more rangeColors values than ranges, excess color values are ignored. If there are more rangeValues values than rangeColors hex colors, the single value appears dark grey if it falls within a range without a color mapped to it.

rangeValues

Number array

none

Use an array of numbers to specify ranges for the single value. Ranges determine single value color if you are using color by value. Use the rangeColors option to specify colors that map to rangeValues values.

showSparkline

boolean

true

Indicate whether to show the single value sparkline, if one is available.

A sparkline is only available for searches that include the timechart search command.

showTrendIndicator

boolean

true

Show or hide the single value trend indicator. A trend indicator is only available when the visualization query includes the timechart command.

trendColorInterpretation

One of the following values.

standardinverse

standard

Specifies whether a field value greater than 0 is shown as a positive (standard) or negative (inverse) trend.

trendDisplayMode

One of the following values.

percentabsolute

absolute

Specifies whether the delta value is displayed as a percentage or an absolute count.

trendInterval

SPL time modifier

auto

Indicate the start time for calculating the trend delta. The trend is evaluated from the start time to the most recent data point.

Use the search syntax for time modifiers to indicate the range.

underLabel

String

Caption for the visualization.

useColors

Boolean

false

Enable or disable color in the visualization. Set to true for value and trend color options to be available.

useThousandSeparators

boolean

true

Specifies whether the numeric value includes thousand separator characters. For example, 1,000 includes a thousand separator.

unit

Brief text label

none

Specify a label to show next to the single value. The unit text should be brief. Typically, an abbreviation, such as MB, or a symbol, such as $, can be used.

unitPosition

One of the following values.

beforeafter

after

Specify whether the unit label should appear before or after the single value.

Deprecated options

Property

Type

Default

Description

Alternatives

additionalClass

CSS class name

CSS class name to add to the result container.

Use colorBy, rangeValues, and rangeColors to configure color mapping for

values.

afterLabel

String

Visualization label

Use underLabel to include a caption or unit to add a measurement unit to the single value.

beforeLabel

String

Visualization label

Use underLabel to include a caption or unit to add a measurement unit to the single value.

classField

String

Adds the value of the classField of the first result as an additional CSS class to the result container.

Use colorBy, rangeValues, and rangeColors to configure color mapping for

values.

linkFields

String

result

Indicates the visualization element clickable for drilldown.

The single value itself is clickable for drilldown. Use the <drilldown> element to configure drilldown behavior.

linkSearch

Search string

Search whose results are clickable for drilldown.

The single value itself is clickable for drilldown. Use the <drilldown> element to configure drilldown behavior.

linkView

Dashboard or form

Dashboard or form used with linkSearch search for drilldown.

Use the <drilldown> element to configure drilldown behavior, including linking to a dashboard or form.

search

Use the <search> element to define a search in a dashboard, form, or panel. You can also use a <search> to define input choices dynamically.

Search types

The <search> element can define any of the following search types.

Search type

Description

Inline

Define a search directly in the dashboard, form, or panel. Use the <query> element to specify the search string. You can add time range modifiers and other options to configure the search.

Report reference

Use a report search and visualization in a panel. Add the ref attribute and the report name to the <search> element.

You can configure the visualization from the referenced report and add custom time range modifiers to the search. You cannot modify the search string in Simple XML. Edit the report to adjust the search string. When you edit a report search, panels with references to the report update automatically.

Populating search for input choices

Use <search> as a child element of a form input to populate choices for checkbox, dropdown, multiselect, or radio inputs. Indicate <fieldForLabel> and <fieldForValue> search result fields to populate the input choice labels and choice values.

Do not use real-time searches for populating searches. Input choice labels and values do not update as real-time search results generate.

Base search

A base search generates transformed results for post-process searches to modify. A base search can be global, defined at the <dashboard> or <form> level. You can also use a base search at the <panel> level in Simple XML.

Make sure that all base searches meet the following requirements.

Use transforming commands in the base search to generate transformed results. Non-transforming base searches can cause performance and timeout issues.

The base search must have an <id> attribute for post-process searches to reference.

Post-process search

A post-process search accepts transformed results from a base search and performs additional search processing on these results. Use the base and id attributes to reference the base search id for a post-process search.

Specify <earliest> and <latest> elements in the base search. A post-process search ignores time modifiers defined within the post-process <search> element.

Element hierarchy

You can put a <search> element into any of the following parent elements.

<form>

<dashboard>

<panel>

<chart>

<event>

<map>

<single>

<table>

Attributes

Name

Type

Default

Description

app

text

The name of an app.

Use the app attribute with the ref attribute to reference a report that is not in the current app.

base

text

In a post-process search, references a base search in this dashboard, form, or panel. Use base with the id attribute to indicate the base search that the post-process search should use.

depends

List of one or more tokens

All of the tokens listed must be defined for the search to dispatch. If the search does not dispatch, the panel does not render.

id

Text (minimum two characters)

Search identifier. In a post-process search, reference the base search using this identifier.

Make sure that search identifiers follow these requirements.

Use only alphanumeric or underscore characters.

The id cannot begin with a number or the underscore character.

The following terms are reserved for internal use and cannot be used for an id.

dashboard

default

footer

header

search

submitted

url

ref

text

Reference to a report. Adds the report search and visualization to the dashboard or form.

If you are referencing a report in another app, use the app attribute to specify the app.

rejects

List of one or more tokens

Stop the search from dispatching if one or more tokens in this list are defined. If the search does not dispatch, the panel does not render.

Child elements

Use the following child elements within a <search>.

Element

Type

Default

Description

<cache>

For saved searches, use one of the following values.

true

false

scheduled

[integer]

scheduled

true: Always use the results from a preexisting saved search job when possible.

false: Never use results from preexisting saved search jobs.

scheduled: Reuse any previously run scheduled saved search jobs.

[integer]: The number of seconds indicating the maximum saved search job results age. Only results that are newer than this number of seconds are used.

<cancelled>

N/A

N/A

Execute actions when a search is cancelled.

<done>

N/A

N/A

Execute actions based on finished search events. Includes job properties and first result row.

<error>

N/A

N/A

Execute actions when there is a search error event, such as an invalid query.

<earliest> and <latest>

text

Optional time expressions that specify the earliest and latest time parameters for a search.

Post-process searches ignore child <earliest> and <latest> elements. Instead, the <earliest> and <latest> elements from the base search are used.

You can specify the time as relative time or absolute time. For relative time, use relative time modifiers, as described in Specify relative time ranges in your search in the Search Manual. For absolute time, specify the time in UNIX epoch time format.

Note: UNIX epoch time format for absolute time in Simple XML is different from the SPL absolute time format used in queries.

<progress>

Execute an action on search progress events. Access job properties and the first results row.

<query>

text

Search string.

<refresh>

Integer or relative time expression

No refresh

Indicate a delay or interval time for inline or saved searches. This setting does not apply to post-process searches, which refresh automatically when their base search refreshes.

Integers are handled as seconds. Use SPL syntax for relative time expressions. For example, 1h5m or 5m.

Use the <refreshType> setting to specify refresh behavior in relation to search completion or dispatch.

You can use the <refresh.display> setting in a visualization to specify a refresh progress indicator.

<refreshType>

interval or delay

delay

Indicate the starting time for counting down to a refresh. Use delay to start counting when the search is done.

Use interval to count down when the search is dispatched. If the runtime of the search is longer than the configured time, the search job is cancelled and a new job is dispatched.

Use the <drilldown> element to start implementing drilldown behavior. The <drilldown> element contains child elements that define the response to a user click.

Drilldown actions
Inside a <drilldown> element, use <set>, <unset>, or <eval> to update token values as part of building dynamic behavior or display in the current dashboard or form. Use <link> to open a search, another dashboard, or an external website. You can pass token values to a linked target on a user click.

Drilldown conditions
Define conditional responses to different user actions by adding a <condition> element within the <drilldown>.

Use actions or conditions as drilldown child elements
You cannot combine actions and conditions as direct child elements of <drilldown>. If you are defining conditional drilldown behavior, you cannot include action elements directly inside the <drilldown> element. If you are defining actions directly inside the <drilldown> element, you cannot add <condition> elements directly inside the drilldown.

Attributes

None

Element hierarchy

Put a <drilldown> element inside any of the following visualization parent elements.

<chart>

<event>

<map>

<single>

<table>

Child elements

Use the following child elements inside a <drilldown> to configure the actions that happen when users click on the element where drilldown is enabled.

set

Set or update token values that other dashboard or form elements can consume. You can set tokens as part of creating dynamic behavior or display, such as passing a user selected value from a form input to a search or managing panel hide/show behavior.

Element hierarchy

Form input

<change>
<condition> (optional)
<set>

Drilldown

<drilldown>
<condition> (optional)
<set>

Attributes

Name

Type

Description

Example

token

Token name

Required. Use the token whose value you are setting or updating.

This example includes the |s$ token filter to indicate that the token value should be handled as a string.

<set token="[token_name]"> sourcetype=$click.value|s$</set>

prefix

text

String to add to the beginning of the token value.

This example includes a quotation mark prefix and suffix around the token value.

unset

Use <unset> to clear a previously set token value. When you unset a token, its value is empty until it is set again. Unsetting token values can help you with implementing dynamic display or other behavior in dashboards and forms.

Attributes

Name

Type

Description

token

Token name

Required. Use the token whose value you are unsetting.

Example

Use <set> and <unset> with depends and rejects in dashboard panels to change the visualization that appears on different user clicks.

Predefined drilldown tokens

Predefined tokens capture information when a user clicks different visualization elements. Depending on the visualization type, you can use different tokens to capture a click location or related data.

chart

Token

Description

$click.name$

X-axis field or category name for the clicked location. Not available if the user clicks the chart legend.

$click.value$

X-axis field or category value for the clicked location. Not available if the user clicks the chart legend.

$click.name2$

Y-axis field or series name for the clicked location. Not available if the user clicks the chart legend.

$click.value2$

Y-axis field or series value for the clicked location. Not available if the user clicks the chart legend.

$row.<fieldname>$

Access any y-axis field value corresponding to the clicked location x-axis. Not available if the user clicks the chart legend.

$row.<x-axis-name>$

Access any x-axis field value corresponding to the clicked location. Not available if the user clicks the chart legend.

$earliest$

Earliest time for the clicked chart segment. If not applicable, uses the earliest time for the search.

$latest$

Latest time for the clicked chart segment. If not applicable, uses the latest time for the search.

event

Token

Description

$click.name$

Field name for the clicked element in the event list. If a field name is not available for the clicked location, the $click.name$ value defaults as follows.

Clicking an element in the event: _raw

Clicking the event timestamp: _time

Clicking a tag: uses the tag name. For example, if host is tagged, uses host.

$click.value$

Field value for the clicked element in the event list.

$click.name2$

Identical to $click.name$.

$click.value2$

Identical to $click.value$.

$row.<fieldname>$

Access any field value in the clicked event. For example, to access the host field value, use $row.host$.

$earliest$

Earliest time for the clicked event. Equivalent to the _time field value. Defaults to the earliest search time.

$latest$

Latest time for the clicked event. Equivalent to one second after the _time field value. Defaults to the latest search time.

map

Predefined tokens are available for cluster and Choropleth maps. Some tokens are only available in cluster maps.

Token

Description

$click.name$

Field name for the clicked location. If multiple fields are associated with the location, uses the first field.

$click.value$

Field value for the clicked location. If multiple fields are associated with the location, uses the first field.

$click.name2$

Same as $click.name$

$click.value2$

Same as $click.value$

$row.<fieldname>$

Access field values related to the clicked location. Check the Statistics tab for available fields.

$earliest$

Earliest time for the search generating the map.

$latest$

Latest time for the search generating the map.

$click.lat.name$

For cluster maps: latitude field name for the clicked location.

$click.lat.value$

For cluster maps: latitude field value for the clicked location.

$click.lon.name$

For cluster maps: longitude field name for the clicked location.

$click.lon.value$

For cluster maps: longitude field value for the clicked location.

$click.bounds.<orientation>$

For cluster maps: south, west, north, or east outer boundary for the clicked location. For example, use $click.bounds.east$ to get the eastern outer boundary.

single value

Token

Description

$click.name$

Name of the field that the single value represents.

In a <condition> element configuring drilldown for a single value, field corresponds to $click.name$.

$click.value$

Field value that the single value represents

$click.name2$

Same as $click.name$.

$click.value2$

Same as $click.value$.

$row.<fieldname>$

Access any field value from the Statistics table row for the single value.

$earliest$

Earliest time for the search that generates the single value

$latest$

Latest time for the search that generates the single value

table

Token

Description

$click.name$

Leftmost field (column) name in the table. Typically, _time is leftmost in a table that includes this field and where columns are ordered by default.

$click.value$

Leftmost field (column) value in the clicked table row.

$click.name2$

Clicked field (column) name. In a <condition> element configuring drilldown in a table, field corresponds to $click.name2$.

$click.value2$

Clicked field (column) value. Use this token to capture the specific table cell value that users click.

$row.<fieldname>$

Access any field (column) value from the clicked table row.

$earliest$

Earliest time for the clicked table row. If not applicable, uses the earliest time of the search.

$latest$

Latest time for the clicked table row. If not applicable, uses the latest time of the search.

trellis

Token

Description

$trellis.name$

Split field name

$trellis.value$

Split field value

Deprecations and removals

Check the Deprecated features list in the Release Notes for additional information on deprecated or removed elements.

Comments

"searchWhenChanged: Boolean: Specifies to run the search when the selection changes" is unclear. Which search? Some input elements will have a search child (used to populate a dropdown, for example). Surely that is not the search being run upon a form input change? I suspect the searches that are run are all the direct children of form or dashboard as well as the indirect children (inside an arbitrary nested set of panels, charts, events, maps, singles or tables).

Note also that the description of the search element does not indicate it can be a child of input.

DUThibault

April 13, 2018

The HTML section makes no mention of the `style` element and including CSS directly in SimpleXML. This seems to work fine, but documentation appears to be missing. I have posted on Answers (https://answers.splunk.com/answers/556491/does-css-included-in-simplexml-have-any-side-effec.html) and the question still remains as to the validity of using the `style` element in `html`. Can someone at Splunk speak to this for the sake of the app developers who would like to know?

Enter your email address, and someone from the documentation team will respond to you:

Send me a copy of this feedback

Please provide your comments here. Ask a question or make a suggestion.

Feedback submitted, thanks!

You must be logged into splunk.com in order to post comments.
Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic.
If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk,
consider posting a question to Splunkbase Answers.

0
out of 1000 Characters

Your Comment Has Been Posted Above

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website.
Learn more (including how to update your settings) here »