# Defining drill-downs per visualization a tad tedious?

**URL:** <https://discuss.elastic.co/t/defining-drill-downs-per-visualization-a-tad-tedious/274143>\
**Category:** Kibana\
**Created:** [May 27, 2021, 7:04am UTC](https://discuss.elastic.co/t/defining-drill-downs-per-visualization-a-tad-tedious/274143 "2021-05-27T07:04:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![GrahamHannington](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grahamhannington/32/4404_2.png) [@GrahamHannington](https://discuss.elastic.co/u/GrahamHannington)\
**Post date:** [May 27, 2021, 7:04am UTC](https://discuss.elastic.co/t/defining-drill-downs-per-visualization-a-tad-tedious/274143/1 "2021-05-27T07:04:34Z")

</div>

...or am I just lazy?

I have several dashboards that show various metrics, such as memory usage and CPU usage, by "job" name. Each dashboard has several "... by Job Name" visualizations.

For each ".. by Job Name" viz, I've defined the same "View job details" drill-down to the same Job Details dashboard. Where the "top-level" dashboards break down data by job name from a particular angle (such as CPU usage or memory usage), the Job Details dashboard is designed to present details about a _single_ job name from _multiple_ angles.

I understand the flexibility that stems from defining drill-downs per visualization—clicking a job name in different charts might go to different dashboards—but for my use case, it means defining the _same_ "View job details" drill-down _multiple_ times.

This is not a complaint. Rather, it's an observation, to see if anyone else has thoughts on this. I don't have a clear feature request in mind, although I can vaguely imagine some "global" drill-down definition ("Whenever a job name is clicked—in any viz, in any dashboard, in this space—offer the option to go to _this_ dashboard.").

Possibly too much info: the original set of dashboards, with the "... by Job Name" visualizations, can, of course, be filtered to show only a single job name. One issue there (although, not the only issue), is what I call _Fat Single Bar Syndrome_ (I'm working on the hyphenation 😉 ): charts designed to show multiple job names, now showing only a single job name; _not_ an optimal use of "dashboard real estate".

---

<div class="post-metadata">

**Author:** ![Aaron\_Caldwell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aaron_caldwell/32/45755_2.png) [@Aaron\_Caldwell](https://discuss.elastic.co/u/Aaron_Caldwell)\
**Post date:** [May 27, 2021, 3:16pm UTC](https://discuss.elastic.co/t/defining-drill-downs-per-visualization-a-tad-tedious/274143/2 "2021-05-27T15:16:14Z")

</div>

Hello,

Agreed there is room for improvement here. Sounds like [this issue](https://github.com/elastic/kibana/issues/85013) is along the lines of what you're thinking? Feel free to comment there if you like.

Regards,  
Aaron

---

<div class="post-metadata">

**Author:** ![GrahamHannington](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grahamhannington/32/4404_2.png) [@GrahamHannington](https://discuss.elastic.co/u/GrahamHannington)\
**Post date:** [May 28, 2021, 3:03am UTC](https://discuss.elastic.co/t/defining-drill-downs-per-visualization-a-tad-tedious/274143/3 "2021-05-28T03:03:35Z")

</div>

Hi @Aaron_Caldwell , thanks for the link to that issue. Yes, I've added a [comment](https://github.com/elastic/kibana/issues/85013#issuecomment-850076181) there.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 25, 2021, 3:04am UTC](https://discuss.elastic.co/t/defining-drill-downs-per-visualization-a-tad-tedious/274143/4 "2021-06-25T03:04:29Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.