Splunk Search

How to accelerate the searches for a dynamic dashboard?

chintan_shah
Path Finder

Hi,
I have a dynamic dashboard which contains multiple panels and it takes a lot of time for displaying the data. Is there any way by which we can accelerate the searches for a dynamic dashboard?

0 Karma

sundareshr
Legend

You will need to optimize each panel by
- create saved search and resuse that `| loadjob'
http://docs.splunk.com/Documentation/Splunk/6.5.0/Viz/Savedsearches

or use post-processes searches
http://docs.splunk.com/Documentation/Splunk/6.5.0/Viz/Savedsearches#Post-process_searches

or, use accelerated data model or summary index to optimize each panel

If you share your dashboard code (relevant parts) we can offer better ideas.

0 Karma

chintan_shah
Path Finder

Thanks Sundareshr for your feedback,
I am currently having dashboard with the below details:
1. Panel which is showing single value with Trend line for the usage of the system in percentage (computing the overall usage vs particular system usage).
2. Panel which is showing bar graph type of system,
3. Bar graph of the details for system usage.
4. Time chart of last 14 days for trending of usage where user can select and drilldown further..
5. There are other 5 panels which are enabled only on click.

0 Karma

sundareshr
Legend

Given the above, a combination of datamodel and post-process searches would be your best option. If you share your dashboard code, we can try and help.

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...