Dashboards & Visualizations

Why do dashboard queries sometimes not complete?

jbrenner
Path Finder

I have a dashboard where some of the chart queries are modified by the value of a dropdown:

  <fieldset submitButton="false" autoRun="true">
    <input type="dropdown" token="time_window_tok" searchWhenChanged="true">
      <label>Select a Time Window</label>
      <choice value="-1week">Past 7 Days</choice>
      <choice value="-1day">Yesterday</choice>
      <default>Past 7 Days</default>
      <change>
          <condition label="Past 7 Days">
               <set token="bins_tok">7</set>
           </condition>
           <condition label="Yesterday">
               <set token="bins_tok">24</set>
           </condition>
      </change>
    </input>
  </fieldset>

Here is one of the queries (I removed everything extraneous):

index=xyz earliest=$time_window_tok|s$ URI="something"
| timechart partial=false bins=$bins_tok$ dc(IP) as MyResult

Sometimes the chart inside the panel displays fine, and sometimes it never renders.
Usually, when you refresh the browser, it displays correctly.
Is there anything wrong with the way I'm doing this? Is there some attribute I can add to the XML to force the dashboard to wait until the queries are rendered?

Thanks,
Jonathan

0 Karma

jbrenner
Path Finder

I just discovered the solution, so I'm going to answer my own question.
The issue has nothing to do with the drop-down, The issue is the use of the "bins" keyword.
When I remove it, the queries always complete.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...