Reporting

TimeRangePicker Module contains HiddenSavedSearch could not use cached saved search?

hjwang
Contributor

as title mentioned, when TimeRangePicker Module contains HiddenSavedSearch just as follows

<module>name="TimeRangePicker" layoutPanel="panel_row2_col1" group="Test" 
  <param name="searchWhenChanged">True</param>
  <param name="default">Last 24 hours</param>
    <module name="HiddenSavedSearch" autoRun="True">
      <param name="useHistory">true</param>
      <param name="savedSearch">Test</param>
      <module name="ViewRedirectorLink">
        <param name="viewTarget">flashtimeline</param>
        <param name="label">View full results</param>
      </module>
      <module name="SimpleResultsTable"></module>
    </module>
</module>

when loading into this view, splunk will says 『No scheduled job was found for saved search "false".』. it must set param useHistory to be false to run correctly. in this case, can i use cached saved search to quickly show results?? thanks in advance.

0 Karma
1 Solution

araitz
Splunk Employee
Splunk Employee

HiddenSavedSearch will not load search artifacts if a TimeRangePicker passes down a time to it.

View solution in original post

0 Karma

araitz
Splunk Employee
Splunk Employee

HiddenSavedSearch will not load search artifacts if a TimeRangePicker passes down a time to it.

0 Karma

hjwang
Contributor

Thanks araitz. I got it. It can not be used in this form.

0 Karma

melting
Splunk Employee
Splunk Employee

First: You will need to schedule and have this job run at least once. Or you can switch the useHistory param to auto to run the search again.

Please see similar question

Second: I don't think you want the save search as a child of a timepicker since the saved search would already have been run over a specified time.

0 Karma

hjwang
Contributor

Thanks for your response,melting. I try to set useHistory param to auto but still not work at all. Splunk shows 『Configuration error - HiddenSavedSearch is being run as a schedule and is configured to listen to the time picker. Scheduled results will not be shown』. I think it's an order of module hierarchy problem. It might not be used in this turn.

0 Karma
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!

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...