Dashboards & Visualizations

Splunk table: fill with previously fetched data

pshrm
New Member

I've a dashboard where one can fill the input values and hit the submit button. I execute a query and show the results in a table.
if someone clicks on a row (drilldown set on row) it opens another dashboard and show the additional information for clicked row.
Here in second dashboard, I had to execute the search query again (with tokens received from first dashboard).
Since I have all the fields from first dashboard (some fields are hidden) and I could pass them to another dashboard via setting the tokens.
Now, how can I use values of passed tokens in table of second dashboard so could avoid running the search query again.
I tried to use html table but with styling and all, i think it's an overkill for such a simple task.

Any help would be appreciated.

0 Karma

ktugwell_splunk
Splunk Employee
Splunk Employee

Hey pshrm,

If you pass the sid to the new dashboard, you can use loadjob command to retrieve the search results.

loadjob

You can access the sid by setting $job.sid$ to a token in your initial search.

          <done>
            <set token="token name">$job.sid$</set>
          </done>

Have a play with it and I hope it helps

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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...