# How do you keep Kibana dashboards readable as more panels get added?

**URL:** <https://discuss.elastic.co/t/how-do-you-keep-kibana-dashboards-readable-as-more-panels-get-added/391589>\
**Category:** Kibana\
**Created:** [November 14, 2026, 6:44pm UTC](https://discuss.elastic.co/t/how-do-you-keep-kibana-dashboards-readable-as-more-panels-get-added/391589 "2026-11-14T18:44:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gelgfirdous](https://avatars.discourse-cdn.com/v4/letter/g/b4bc9f/32.png) [@gelgfirdous](https://discuss.elastic.co/u/gelgfirdous)\
**Post date:** [November 14, 2026, 6:44pm UTC](https://discuss.elastic.co/t/how-do-you-keep-kibana-dashboards-readable-as-more-panels-get-added/391589/1 "2026-11-14T18:44:39Z")

</div>

I have been thinking about dashboards that start simple and then keep growing. Each new panel adds value, but after a while the dashboard can feel crowded and hard to read.

What helps you keep a Kibana dashboard readable as more panels get added? Do you split it into separate dashboards, group related panels together, remove panels that are rarely used, or use a different layout?

I am curious what habits keep a busy dashboard useful for everyone who opens it.

---

<div class="post-metadata">

**Author:** ![alexanderdavis](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@alexanderdavis](https://discuss.elastic.co/u/alexanderdavis)\
**Post date:** [November 16, 2026, 10:25am UTC](https://discuss.elastic.co/t/how-do-you-keep-kibana-dashboards-readable-as-more-panels-get-added/391589/2 "2026-11-16T10:25:28Z")

</div>

I’d start by giving each dashboard one clear job and audience, then split when a second job appears. Within a dashboard, put the small set of headline metrics in a top row, group related panels under headings, and use consistent time ranges and titles so people can scan it quickly. Prefer drilldowns from summary panels over adding every detail at the top level. Also review usage periodically and archive rarely used panels rather than deleting them outright. The goal is not fewer panels for its own sake, but fewer competing focal points.

---

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [November 16, 2026, 11:07am UTC](https://discuss.elastic.co/t/how-do-you-keep-kibana-dashboards-readable-as-more-panels-get-added/391589/3 "2026-11-16T11:07:35Z")

</div>

> [@gelgfirdous](#):
>
> Each new panel adds value, but after a while the dashboard can feel crowded and hard to read.  
> ...  
> I am curious what habits keep a busy dashboard useful for everyone who opens it.

Each additional panel really adds _value_ to the same people? I think many of us have fought with this issue for years.

My personal difficulty is that often "everyone" said they wanted a single dashboard view, and that requirement eventually becomes the unrealistic bit. We'd like to see the session rate, we'd like to see the geographic breakdown, we'd like to see the hot products, how does this compare to yesterday, last week, and so on. If you want "everyone" to see a "single pane of glass" view, at some point you have to split "everyone" into groups, and limit what each group sees.

One way, showing my age, is to think of a Dashboard view as a PowerPoint slide. We've all seen the PowerPoint slide that is useless as it contains way too much information, and a Dashboard view that has the same issue will not be fit for purpose.

---

<div class="post-metadata">

**Author:** ![gelgfirdous](https://avatars.discourse-cdn.com/v4/letter/g/b4bc9f/32.png) [@gelgfirdous](https://discuss.elastic.co/u/gelgfirdous)\
**Post date:** [November 17, 2026, 8:32am UTC](https://discuss.elastic.co/t/how-do-you-keep-kibana-dashboards-readable-as-more-panels-get-added/391589/4 "2026-11-17T08:32:51Z")

</div>

Thanks both, this is really helpful. The 'one dashboard, one job' idea is the one I am going to try first, along with a headline row of the most important numbers at the top. The slide comparison made me laugh because it is exactly right — ours had become a wall of panels nobody actually reads. I will try splitting the busiest one this week and see if it reads better. Do you review your dashboards on any kind of schedule, or just tidy them up when someone complains?

---

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [November 17, 2026, 10:31am UTC](https://discuss.elastic.co/t/how-do-you-keep-kibana-dashboards-readable-as-more-panels-get-added/391589/5 "2026-11-17T10:31:33Z")

</div>

Good luck. It's actually really hard to keep focus on this on a long term basis, so it's a very decent idea is to hard-code a regular review, monthly, quarterly, whatever suits you.

The other analogy I often use is the car dashboard. The driver is the main audience. Once what are effectively passenger requirements start getting added it can actually get dangerous. For the "main" operational dashboard, focus on your equivalent of the driver, and anything that the driver doesn't **need** to know should be somewhere else.

And if/when you have a "wall of panels" then maybe that should be on an actual physical wall 🙂
