Dashboards & Visualizations

Dashboard Studio: How to create a input dropdown from datasource?

squared_away
Engager

Hello,

I have a number of unique searches for various infrastructure resources. I would like to create a dashboard that builds a chart based on the chosen entry from a dropown. Unfortunately, there's no easy way to create a base search and use tokens.

In other words, I would like each input title to reference a specific search in datsources.

example dropdown: 

input selected value 1= "dataSources": "search_1"

input selected value 2 = "dataSources": "search_2"

input selected value 3 = "dataSources": "search_3"

I could not find any documentation with examples of something similar.

Thanks in advance.

Labels (1)
Tags (2)
0 Karma
1 Solution

squared_away
Engager

I solved the challenge on my own.

I created multiple input items and used the search as the value. Then, I used the token from the input as the primary datasource.

Example

"input_1": {
"options": {
"items": [
{
"label": "Metric 1",
"value": "| mstats ***unique-search-string1******"
},
{
"label": "Metric 2",
"value": "| mstats ***unique-search-string2******"
},
{
"label": "Metric 3",
"value": "| mstats ***unique-search-string3******"
}
],
"defaultValue": "",
"token": "hosts_tok"
},
"dataSources": {
"primary": "$hosts_tok$"
},
"title": "Hosts",
"type": "input.dropdown"
}

If there's a better way please let me know.

View solution in original post

squared_away
Engager

I solved the challenge on my own.

I created multiple input items and used the search as the value. Then, I used the token from the input as the primary datasource.

Example

"input_1": {
"options": {
"items": [
{
"label": "Metric 1",
"value": "| mstats ***unique-search-string1******"
},
{
"label": "Metric 2",
"value": "| mstats ***unique-search-string2******"
},
{
"label": "Metric 3",
"value": "| mstats ***unique-search-string3******"
}
],
"defaultValue": "",
"token": "hosts_tok"
},
"dataSources": {
"primary": "$hosts_tok$"
},
"title": "Hosts",
"type": "input.dropdown"
}

If there's a better way please let me know.

muhammad_luthfi
Path Finder

Amazing!, thanks brother @squared_away , got your idea, i'm prefer using saved search because applicable for form.token , instead of put SPL query under value because required add backslash \

 it's very simple we just create simple form

{
    "type": "input.dropdown",
    "title": "Testing Multi Query",
    "options": {
        "items": [
            {
                "label": "Query 1",
                "value": "| makeresults | eval key=\"value\" | table *"
            },
            {
                "label": "Query 2",
                "value": "| loadjob savedsearch=\"admin:itsi:sla_availability\" artifact_offset=0"
            },
            {
                "label": "Query 3",
                "value": "| savedsearch \"AWS - IPs available\""
            }
        ],
        "token": "tos",
        "defaultValue": ""
    }
}

 

And create the visualization with my example token $tos$ bellow :

muhammad_luthfi_0-1749174627981.png

 

0 Karma

VatsalJagani
SplunkTrust
SplunkTrust

@squared_away - Kindly approve your own answer by clicking on the "Accept as Solution" button.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...