Is it possible to use a scheduled report as the base search in a dashboard?

[sylbaea]

Hello,

I am using Splunk 6.5

I would like to leverage scheduled report capability to speed up dashboard rendering.

1. I have a complex report making a search like search (...) | table A, B, C where (...) is a complex query made of dedup, lookup, eval, etc. commands.
2. I scheduled this report to be computed every hour
3. I check I get the expected result

4. Then I try to define this scheduled search as parent search of a dashboard like following...

   <form>
     <search id="CurrentTickets" ref="my report">
     </search>
       (...)
             <single>
           <search base="CurrentTickets">
             <query>stats count by A</query>
           </search>
         </single>
       (...)
   

   When I try to display the dashboard, it does not display anything (trying to search forever).
   On the other hand, if I replace the parent search by:

   
   search (...) | table A, B, C
   
   In this case, it displays as expected, but of course not with the expected performance as it does computer real-time my search.

Is it possible to combine a scheduled report with parent search concept?

Regards.

Sylvain

[rlacher]

I was Googling around for this same thing and found your post. Swapping ref and id worked for me, strangely.

<search ref="my report" id="CurrentTickets">
    <earliest>$TOKEN_TIME.earliest$</earliest>
    <latest>$TOKEN_TIME.latest$</latest>
</search>

I tried using query tags as well per cmerriman's answer, but the search wouldn't fire off until I removed them.

[cmerriman]

try adding a query tag:

<search id="CurrentTickets" ref="my report">
<query> fields *</query>
       </search>

[sylbaea]

Thanks for the suggestion... Strangely, with this change, the panels in the dashboard starts to render their content but very very slow, even slower than when the search is executed live.

[cmerriman]

possibly try to do a fields a, b, c instead of fields * in case it's bringing back unexpected fields?

[sylbaea]

I tried, same result unfortunately.

[robertlynch2020]

did you get this to work in the end?