Dashboards & Visualizations

Why does "Search is waiting for input" has a delay if using loadjob and JS?

nick405060
Motivator

Main search:

makeresults | append [| loadjob "$exchange$"] | eval trigger="$submit_trigger1$"

where the ad-hoc loadjob sets $exchange$ via

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

However, the "search is waiting for input" message does not go away until $job.sid$ is populated. Changing <done> to <progress> does not fix the issue. Isn't this an inherent drawback to using loadjob as a replacement for post-processing with its many faults (unable to do multiple base searches, export button grayed out)? Are there any workarounds or fixes?

nick405060
Motivator

One workaround is to use <table depends="$exchange$"> to hide results until completion, and then make your own HTML message:

  <search>
    <query>
| makeresults | eval trigger="$submit_trigger1$" | eval message="Your search is running..." | table message
    </query>
    <progress>
      <set token="submitted_message">$result.message$</set>
    </progress>
  </search>
  <search>
    <query>
| makeresults | eval trigger="$exchange$" | eval message="Your search is complete." | table message
    </query>
    <progress>
      <set token="submitted_message">$result.message$</set>
    </progress>
  </search>  
0 Karma
Get Updates on the Splunk Community!

Strengthen Your Future: A Look Back at Splunk 10 Innovations and .conf25 Highlights!

The Big One: Splunk 10 is Here!  The moment many of you have been waiting for has arrived! We are thrilled to ...

Now Offering the AI Assistant Usage Dashboard in Cloud Monitoring Console

Today, we’re excited to announce the release of a brand new AI assistant usage dashboard in Cloud Monitoring ...

Stay Connected: Your Guide to October Tech Talks, Office Hours, and Webinars!

What are Community Office Hours? Community Office Hours is an interactive 60-minute Zoom series where ...