Set multiple tokens within form inputs to drive multiple searches, better labeling, and more.
Key use cases include:
Set tokens for both label and value to use throughout your dashboard. Use this to create a special empty/null choice that includes a unique token transformation. Use the selection of a given form input to unset other tokens on the page. Create a "simple" time range picker dropdown input that sets a unique earliest and latest token. Set multiple tokens based on search results. How it Works
Ability to set/unset multiple tokens within a form input is only available via the XML editor. Functional gets triggered on a user selected change event, <change>. Add conditions if you want to set/unset specific tokens and values based on user selection. conditions can be based on user selected values, <condition value="last_24hr">. conditions can be based on user selected labels, <condition label="Last 24 hours">. wildcard (partial matching) is NOT support in conditions. asterisk ("*") is interpreted as all other values, <condition value="*">. Note - conditions are not supported for multiselect and checkbox form inputs (any multivalue input). You have the following click information available for use in set/unset, $label$, $value$. For dynamic choices where you run a search, you can set tokens based on search results, $row.field_name. set and unset syntax works identical to contextual drilldown. <set token="my_token_value">$value$</set> <set token="my_token_label">$label$</set> <set token="my_token">field=$value|s$</set> <set token="my_token" prefix="(" suffix=")" delimiter=" OR ">field=$value|s$</set> <set token="my_token">$row.sourcetype$</set> <unset token="showTable"/> Use a static choice "ANY" to represent an empty/null value, where it searches for events both with and without the existence of the field.
Available from 6.3 onwards –
Color Modes Not all maps are created equal. Depending on the use case, you will want to use one of three color modes: 1) Sequential: One color, different shades. Choose this to show the distribution of a variable across a geographic region. 2) Divergent: Two colors, different shades, converging at a white neutral point. Choose this to show how much a variable is above or below a neutral point.</li> 3) Categorical: Different colors, one per category. Choose this to color areas of your maps according to different distinct values.</li>
| lookup geo_sf_neighborhoods latitude AS location.lat, longitude AS location.long OUTPUT featureId AS neighborhood
Splunk Dashboarding & Universal Vs. Heavy Forwarders
• Housekeeping: Overview & House Rules
• Presentation & Demo: Creating Awesome Dashboards
• Group Discussion: Sharing Dashboarding Tips & Tricks
• Presentation: Universal vs. Heavy vs. Intermediate Forwarders
• Group Discussion: Latest Splunk Challenges / Solutions
Splunk [Official] User Group
“The overall goal is to create an authentic, ongoing
user group experience for our users, where
they contribute and get involved”
● User Lead Technical Discussions
● Sharing Environment
● Build Trust
● No Sales!
Grab you phone and go to:
Tips & Tricks
Universal Vs. Heavy
Based on Darren Dance’s Blog
Universal Vs. Heavy (+ Intermediate) Forwards
● Smallest Footprint
● Standard Data
● Un-Parsed /
No Event Breaking
● Larger Footprint
● Full Splunk Enterprise
● Allows Filtering at
Source / In-Flight
● UF or HF Binaries
● Aggregation Layer
● Artificial Bottleneck
● Performance Impact
Heavy Forwarders Are[n’t] Awesome!
The use of Heavy Forwarders were once commonly advised, but times change…
● Previous advice for using Heavy Forwarders
– Filtering of data is best done at source and HF are required as UF cannot parse.
– Use for aggregation layer for central management of data flows.
‣ Can cause data imbalance on the indexing tier that will reduce search performance.
● Reasons for NOT using Heavy Forwarder
– Filter data at the Indexers. Greater use of compute resources / more performant.
– Reduces network usage / IO by a significant degree.
– Reduces the time from event generation to search availability.
– Segmentation doesn’t always reduce threat vector for application exploitation.
Test Setup: File Contained 367,463,625 Events
Yes 39.1 1,941 5,092 21,151
No 38.4 1,922 5,139 20,998
Yes 6.5 863 14,344 7,923
No 6.4 1,015 17,466 6,662
● The amount of data sent over the network was approximately 6 times
lower with the Universal Forwarder.
● The amount of data indexed per second was approximately 3 times
higher when collected by a Universal Forwarder.
● The total data set was indexed approximately 6 times quicker when
collected by the Universal Forwarder.
What About Network Segmentation?
● Limited Reduction to Application Threat Vector (UF > IF > IX)
– If the Splunk software on the IF are vulnerable, then the same exploit could be
used to pivot into the next network layer anyway.
● Network Load
– If using a HF to aggregate the forwarder traffic, the additional network load
could be upwards of 6x more than if UF directly to Indexers (Raw Vs. Parsed
Exceptions to UF > HF
Some exceptions to using Universal Forwarders over Heavy Forwarders
● Special App Requirements
– DB Connect / eStreamer / Opsec LEA / Etc.
● Modify In-Flight Events (Parsed Data Stream)
– Change data before it leaves a specific environment (pattern replacement).
● Routing Based on Event Contents
– Route data based on criteria such as source or type of event.
Updates Announced at .conf 2016
● Introducing Splunk Enterprise 6.5 - Available Now
‣ Splunk ML Toolkit: Guided workbench and SPL extensions to help you create and
operationalize your own custom analytics based on your choice of algorithms.
‣ Tables: New feature that lets you create and analyse tabular data views without
‣ Hadoop Data Roll: Gives you another way to reduce historical data storage costs
while keeping full search capability.
● Premium Apps - New Releases:
– Splunk Enterprise Security [Minor Release]
– Splunk IT Service Intelligence [Major Release]
– Splunk User Behaviour Analytics [Major Release]
● Splunk User Group Edinburgh
● Splunk’s Slack Group
– Register via www.splunk402.com/chat
– Channel: #edinburgh
● Present & Share at the User Group?
‣ Harry McLaren | email@example.com | @cyberharibu | harrymclaren.co.uk
‣ ECS | firstname.lastname@example.org | @ECS_IT | ecs.co.uk