Splunk Enterprise

Help on drilldown token

jip31
Motivator

hello

as you can see, I use a token in order to drilldown from a table panel to another table panel

        <drilldown>
          <set token="host">$click.value$</set>
        </drilldown>
      </table>
    </panel>
  </row>
  <row>
    <panel>
      <table>
        <title>% de paquets VMware perdus</title>
        <search>
          <query>`index`(sourcetype=netproc_tcp" host=$host$
 

but when I refresh te dashboard my second panel says "waiting for input"

jip31_0-1656220535542.png

is there a solution to always display the events in the second panel and to drilldown when I click on the token field?

thanks

 

 

Tags (1)
0 Karma
1 Solution

bowesmana
SplunkTrust
SplunkTrust

At the start of your XML add an <init> section and set a default for the host token, i.e.

<form>
  <init>
    <set token="host">*</set>
  </init>
...

so when the dashboard first loads, or is refreshed, the default for the 'host' token will be all hosts and the second panel will show all hosts.

 

View solution in original post

0 Karma

bowesmana
SplunkTrust
SplunkTrust

At the start of your XML add an <init> section and set a default for the host token, i.e.

<form>
  <init>
    <set token="host">*</set>
  </init>
...

so when the dashboard first loads, or is refreshed, the default for the 'host' token will be all hosts and the second panel will show all hosts.

 

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @jip31,

to be more sure, I'd need to see the search, anyway, having a table, please try to use:

<set token="host">$row.host$</set>

$click.value$ is for drilldown from graphs.

Ciao.

Giuseppe

0 Karma

jip31
Motivator

Hi

This returns an empty result...

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 ...