Dashboards & Visualizations

Is loadjob compatible with a javascript submit button when used as a base search?

nick405060
Motivator

I use JS submit buttons because the SimpleXML submit button is useless (searchWhenChanged is broken, you can only have one button, cannot inline, cannot have multiple, and cannot have multiple timepickers, + many other issues). However, unfortunately, post-processing is also useless (export is broken, you can only use a single base search per post-process) so I would like to use loadjob as a base search.

However, there is inherently an issue in doing so. If you do something like the below:

... | append [| loadjob "$exchange$"] | append [| loadjob "$badge$"] | append [| loadjob "$wineventlog$"] | eval trigger="$submit_trigger1$"

Then on the first run the search is going to wait until all tokens have been populated because they start as null. This means that when you click submit the first time the "search is waiting for input" message is going to stay. The second submission onwards, the "search is waiting for input" message will function as normal and change since no tokens are null any longer, but also the search will keep getting updated each time another base search has completed, instead of just once when they all have completed.

Is Splunk capable of using multiple base searches per post-process, AND using a normal, non-broken submit button?

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...