Dashboards & Visualizations

Token transfer between different dashboards using SplunkJS

MikeJu25
Path Finder

My source dashboard has a clickable table and once a user clicks a row the user will be taken to a destination dashboard and the token will be set to database_id which is then passed in to run a search on the destination dashboard. Now both two dashboards are using a single JS file. But I realized that the token will not be successfully passed in to the search as the token value is not set when the destination dashboard reads the JS file. Could someone please provide help on how should I transfer the token value between two dashboards using SplunkJS? Thank you in advance!

Here's the code for event handler on the source dashboard:

 

allassetstable.on("click", function(e) {
        // Bypass the default behavior
        e.preventDefault();
        // set token name and value
        tokenSet.set("databaseID_tok", e.data.click.value);
        // link back to asset-specific anomalies page
        utils.redirect("Ano","_blank"); 
    });

 

 

Below is the code for search on the destination dashboard:

 

    var search2 = new SearchManager({
        id: "ano",
        preview: true,
        cache: true,
        latest_time: "now",
        search: "index=anomalies database_id=$databaseID_tok$"
    }, {tokens: true});

 

 

 

Labels (3)
0 Karma
1 Solution

kamlesh_vaghela
SplunkTrust
SplunkTrust

@MikeJu25 

Can you please try this?

allassetstable.on("click", function(e) {
    // Bypass the default behavior
    e.preventDefault();
    // set token name and value
    // tokenSet.set("databaseID_tok", e.data.click.value);
    // link back to asset-specific anomalies page
    utils.redirect("Ano?databaseID_tok="+e.data.click.value,"_blank"); 
});

 

Thanks
KV
▄︻̷̿┻̿═━一

If any of my reply helps you to solve the problem Or gain knowledge, an upvote would be appreciated.

View solution in original post

kamlesh_vaghela
SplunkTrust
SplunkTrust

@MikeJu25 

Can you please try this?

allassetstable.on("click", function(e) {
    // Bypass the default behavior
    e.preventDefault();
    // set token name and value
    // tokenSet.set("databaseID_tok", e.data.click.value);
    // link back to asset-specific anomalies page
    utils.redirect("Ano?databaseID_tok="+e.data.click.value,"_blank"); 
});

 

Thanks
KV
▄︻̷̿┻̿═━一

If any of my reply helps you to solve the problem Or gain knowledge, an upvote would be appreciated.

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

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...