Dashboards & Visualizations

Dashboard with multiple searches and multiple users opening dashboard

jordanking1992
Path Finder

Hello,
If a user creates a dashboard with 10 searches and has 10 members of his team open up this dashboard, does this execute 100 searches (10 per each user of the dashboard refresh)? If so, how to we manage this in a scenario where this dashboard is needed often? We are thinking this behavior is responsible for high cpu as there are so many searches being executed each time the dashboard is opened.

Thoughts?

0 Karma
1 Solution

woodcock
Esteemed Legend

Yes, 100 searches. There are several ways to improve this, most of which can be used together.
First, think about using a base search and post-process searches to drive the panels.
Next, think about using the trellis feature to create many multiple panel views from a single search.
Last, consider using a scheduled search to create the data every few minutes or every hour and then | savedsearch to load the data in from the already-run search artifacts.

View solution in original post

woodcock
Esteemed Legend

Yes, 100 searches. There are several ways to improve this, most of which can be used together.
First, think about using a base search and post-process searches to drive the panels.
Next, think about using the trellis feature to create many multiple panel views from a single search.
Last, consider using a scheduled search to create the data every few minutes or every hour and then | savedsearch to load the data in from the already-run search artifacts.

View solution in original post

kamlesh_vaghela
SplunkTrust
SplunkTrust

@jordanking1992

I think the below link will help you to understand concurrent users and searches impact performance.

https://docs.splunk.com/Documentation/Splunk/7.3.2/Capacity/Accommodatemanysimultaneoussearches

0 Karma
Register for .conf21 Now! Go Vegas or Go Virtual!

How will you .conf21? You decide! Go in-person in Las Vegas, 10/18-10/21, or go online with .conf21 Virtual, 10/19-10/20.



This widget could not be displayed.
Get Updates on the Splunk Community!
This widget could not be displayed.