Dashboards & Visualizations

How many panels are recommended in a dashboard?

rishma
Explorer

Hi,

I am seeing that maximum limit of rows in a dashboard is hardcoded as 50 . Is there any recommendation for number of panels in a dashboard?

Tags (2)
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

Finding a reasonable recommendation that works for many use cases is hard, Splunk use varies too much for that. However, I've yet to come across a use case where more than 50 panels, let alone more than 50 rows were the best way to go.

If that 50 row limit is stopping you from building your dashboard to your requirements, check if there are any "natural" ways of splitting up the data. Common splits are on detail level - providing a wider view first and drilling into more detailed views -, on application level - providing a whole-system overview first and drilling into applications or systems -, on departmental concerns - again starting from an overview, and drilling into operations, development, CRM, marketing, whatever views -, or simply by turning a dashboard listing ALL the servers into a form that lets you select what servers you want to see.
As a bonus, it'll make the individual dashboards much faster to load, less of a strain on the browser, and increase the chance of the user actually getting to view the data he needs rather than scrolling for miles to find it.

View solution in original post

nfilippi_splunk
Splunk Employee
Splunk Employee

Are you seeing this in advanced xml or simple xml dashboards?

0 Karma

rishma
Explorer

Simple XML Dashboards.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Finding a reasonable recommendation that works for many use cases is hard, Splunk use varies too much for that. However, I've yet to come across a use case where more than 50 panels, let alone more than 50 rows were the best way to go.

If that 50 row limit is stopping you from building your dashboard to your requirements, check if there are any "natural" ways of splitting up the data. Common splits are on detail level - providing a wider view first and drilling into more detailed views -, on application level - providing a whole-system overview first and drilling into applications or systems -, on departmental concerns - again starting from an overview, and drilling into operations, development, CRM, marketing, whatever views -, or simply by turning a dashboard listing ALL the servers into a form that lets you select what servers you want to see.
As a bonus, it'll make the individual dashboards much faster to load, less of a strain on the browser, and increase the chance of the user actually getting to view the data he needs rather than scrolling for miles to find it.

Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

 (view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...