# How to exclude the Other bucket from Horizontal Bar visualization **URL:** \ **Category:** Kibana\ **Created:** [April 26, 2019, 9:54am UTC](https://discuss.elastic.co/t/how-to-exclude-the-other-bucket-from-horizontal-bar-visualization/178614 "2019-04-26T09:54:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![dplanella](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dplanella/32/45080_2.png) [@dplanella](https://discuss.elastic.co/u/dplanella)\ **Post date:** [April 26, 2019, 9:54am UTC](https://discuss.elastic.co/t/how-to-exclude-the-other-bucket-from-horizontal-bar-visualization/178614/1 "2019-04-26T09:54:14Z")
We're using Kibana 6.1.4 (via [bitergia.io](http://bitergia.io)) to visualize community contribution data to a project. One of the visualizations we're trying to set up is a bar chart of the top 20 contributor names ordered by their number of contributions. We've set up a Horizontal Bar visualization that does just that: ![Bar-chart-data](https://us1.discourse-cdn.com/elastic/original/3X/4/0/400e316596fa8836a82adefcdc8e85a007f7f779.png) ![Others](https://us1.discourse-cdn.com/elastic/original/3X/4/0/404d6492a59b635260ed8837ef9cf4621a9d9729.png) The "Others" bucket is added automatically in the visualization and we have no control over it. The only workaround we've found to diminish the impact it has on the scale of the Y axis is to check "Set Axis Extents" in "Metrics & Axes" to manually set the "Max" value of the Y axis to be near the maximum value of the contribution count of the top contributor, thus truncating the "Others" bar. Using the "Exclude" field under "Buckets" to exclude `Others` did not work. In summary, we'd like to remove the "Others" bucket from the chart and display only the 20 buckets with the user names. Is this possible? ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [April 26, 2019, 4:00pm UTC](https://discuss.elastic.co/t/how-to-exclude-the-other-bucket-from-horizontal-bar-visualization/178614/2 "2019-04-26T16:00:47Z")
Hey @dplanella, I'm unable to replicate what you're seeing. Would you mind checking both of your JSON inputs which I've highlighted below: ![54%20AM](https://us1.discourse-cdn.com/elastic/original/3X/1/5/1521ede88bbbef66c1167b37f28fbc5f621c44ae.png) ---
**Author:** ![dplanella](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dplanella/32/45080_2.png) [@dplanella](https://discuss.elastic.co/u/dplanella)\ **Post date:** [April 26, 2019, 4:38pm UTC](https://discuss.elastic.co/t/how-to-exclude-the-other-bucket-from-horizontal-bar-visualization/178614/3 "2019-04-26T16:38:04Z")
Thanks @Brandon_Kobel for the quick reply. Both JSON input boxes are empty (Metrics \> Y-Axis \> Advanced and Buckets \> X-Axis \> Advanced). > [@Brandon\_Kobel](#): > > I'm unable to replicate what you're seeing. I thought this might be related to the relatively old Kibana version we have. But seeing that you cannot reproduce it, and digging deeper, it looks like we're not running Kibana per se, but a fork of it =\> [GitHub - chaoss/grimoirelab-kibiter: Soft fork of Kibana, for the benefit of GrimoireLab](https://github.com/chaoss/grimoirelab-kibiter). So perhaps this issue only applies to Kibiter. In any case, all the source data is public, and the dashboard itself as well, so here is a link if it makes debugging easier: [https://gitlab.biterg.io/goto/0f3e693d78c6c6947c6780254011d311](https://gitlab.biterg.io/goto/0f3e693d78c6c6947c6780254011d311) ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [April 26, 2019, 5:01pm UTC](https://discuss.elastic.co/t/how-to-exclude-the-other-bucket-from-horizontal-bar-visualization/178614/4 "2019-04-26T17:01:12Z")
The others bucket is being hard-coded by the fork here: [https://github.com/chaoss/grimoirelab-kibiter/pull/51/files](https://github.com/chaoss/grimoirelab-kibiter/pull/51/files) ---
**Author:** ![dplanella](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dplanella/32/45080_2.png) [@dplanella](https://discuss.elastic.co/u/dplanella)\ **Post date:** [April 26, 2019, 9:34pm UTC](https://discuss.elastic.co/t/how-to-exclude-the-other-bucket-from-horizontal-bar-visualization/178614/5 "2019-04-26T21:34:14Z")
Argh, then I guess there is no way to discard or hide the "Others" bucket in this case. Thanks again @Brandon_Kobel for going the extra mile of even checking the fork's code, really appreciated! ---
**Author:** ![dplanella](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dplanella/32/45080_2.png) [@dplanella](https://discuss.elastic.co/u/dplanella)\ **Post date:** [April 30, 2019, 8:38am UTC](https://discuss.elastic.co/t/how-to-exclude-the-other-bucket-from-horizontal-bar-visualization/178614/6 "2019-04-30T08:38:25Z")
I've ended up finding a workaround: Add a Split Series sub-bucket, with a Filters aggregation. Then set the filter to `*` . This effectively shows all results and bypasses `Others` . See it [here](https://gitlab.biterg.io/goto/e510c88f0f5e9462546b3253b014ecce) in action. ![filters](https://us1.discourse-cdn.com/elastic/original/3X/f/e/fe49fd1cf404c3f6f72c127adb2ed087a6d90b76.png) The only downside is that the legend's label shows "\*" (adding a label to the filter ends up adding two legends, one for each bucket, which is confusing). I wonder if there a way to remove legends alltogether? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 28, 2019, 8:38am UTC](https://discuss.elastic.co/t/how-to-exclude-the-other-bucket-from-horizontal-bar-visualization/178614/7 "2019-05-28T08:38:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.