Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Dashboards & Visualizations
×
Are you a member of the Splunk Community?
Sign in or Register with your Splunk account to get your questions answered, access valuable resources and connect with experts!
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Find Answers
- :
- Using Splunk
- :
- Dashboards & Visualizations
- :
- Re: Using URL parameters to set input. Conditions...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Using URL parameters to set input. Conditions with match not setting tokens.
RobKelley06
Explorer
06-24-2021
02:03 PM
I have a link on one dashboard
<html>
<a href="....._dashboard?form.dcCell=$dcCell$&form.rhel=$rhel$&form.field1.earliest=$field1.earliest$&form.field1.latest=$field1.latest$">PRD Dashboard</a>
</html>The link is filling out correctly. When I click it and go to the target dashboard, the inputs are being set correctly, but the tokens are not being set at all.
Target dashboard
<fieldset submitButton="false" autoRun="true">
<input type="dropdown" token="rhel" searchWhenChanged="true">
<label>RHEL Server</label>
<choice value="rhel6">RHEL 6</choice>
<choice value="rhel8">RHEL 8</choice>
<change>
<condition match="match($rhel$,"rhel6") AND match($dcCell$, "allE")">
<set token="use_jcs">True</set>
<set token="use_hikari">True</set>
</condition>
<condition match="match($rhel$,"rhel8") AND match($dcCell$, "allE")">
<set token="use_hikari">True</set>
<unset token="use_jcs"></unset>
When using the drop downs, everything works fine. It's only when i try to put the parameters in the url, does it break. I have even tried using the drop downs and the copying the url it generates on the browser and going directly to that. It still does not set the tokens. What am I missing?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ITWhisperer
SplunkTrust
06-24-2021
02:18 PM
Try using token modifiers
<html>
<a href="....._dashboard?form.dcCell=$dcCell|n$&form.rhel=$rhel|n$&form.field1.earliest=$field1.earliest|n$&form.field1.latest=$field1.latest|n$">PRD Dashboard</a>
</html>- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
RobKelley06
Explorer
06-25-2021
06:33 AM
The URL is not the issue. It's the target dashboard not determining the tokens. I have used the exact URL that changing the dropdowns produces in the browser URL and it still doesn't work. I know the URL works correctly because the dropdowns are changing based off of the URL, but the tokens inside the "condition" statements are not being calculated.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ITWhisperer
SplunkTrust
06-25-2021
09:35 AM
It looks like the change handler for the dropdown is not triggered when the dashboard loads. You could try using a hidden text input to relay the change.
<form>
<label>Token setter</label>
<description>Inputs to set multi-select tokens</description>
<fieldset submitButton="false" autoRun="true">
<input type="multiselect" token="preselect" searchWhenChanged="true">
<label>Select</label>
<choice value="W">w</choice>
<choice value="X">x</choice>
<choice value="Y">y</choice>
<choice value="Z">z</choice>
<default>X</default>
<change>
<condition match="match($preselect$,"[XYZ]")">
<eval token="gettoken">"form.inbound=".mvjoin(split(preselect," "),"&form.inbound=")</eval>
</condition>
</change>
</input>
<html>
<a target="_blank" href="/app/answers/token_getter?$gettoken|n$">Go to getter</a>
</html>
</fieldset>
</form><form>
<label>Token getter</label>
<description>Multi-select initialised on call</description>
<fieldset submitButton="false" autoRun="true">
<input type="multiselect" token="preselect" searchWhenChanged="true">
<label>Pre-select</label>
<choice value="W">w</choice>
<choice value="X">x</choice>
<choice value="Y">y</choice>
<choice value="Z">z</choice>
<default>X</default>
<change>
<condition match="match($preselect$,"[XYZ]")">
<set token="changedtoken">$value$</set>
</condition>
</change>
</input>
<html>
<p>Changed token now $changedtoken$</p>
</html>
<input type="text" token="inbound" searchWhenChanged="true" depends="$alwayshide$">
<label>Received token</label>
<change>
<set token="form.preselect">$value$</set>
</change>
</input>
</fieldset>
</form>You might have to something a bit more fancy for multi-selects
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!
Tech Talk Recap | Mastering Threat Hunting
Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...
Observability for AI Applications: Troubleshooting Latency
If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...
Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?
In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...
