Dashboards & Visualizations

How do you dynamically pass parameters over two dashboards?

arkonner
Path Finder

I defined a lookup file with

Country Router lat lon Name Town
EG AA368Z 30.0771 31.2859 Egypt Cairo
.
.
.
With a search using a geostat command, I show the various router on the map (dashboard1)

On the map selecting the "dot" corresponding to one specific location, I was looking to pass this parameter to another dashboard.

That way, I could run searches only for the selected router/country.

Any help will be useful

0 Karma

scelikok
SplunkTrust
SplunkTrust

Hi arkonner,

You can easily pass any clicked value to another dashboard using Drilldown setting of the map.

Your destination dashboard should have an input that selects router/county.

  • Lets's say destination token name is router_token and map field name on your source dashboard is router_name.
  • On drilldown editor select Link to dashboard as On Click event, choose relevant App and Dashboard.
  • On Advanced>Parameters you should set as form.router_token = $row.router_name$

When you click on a router on the map it will open the destination dashboard with router_tokenvalue set.

I hope this helps.

If this reply helps you an upvote and "Accept as Solution" is appreciated.
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 ...