# Heatmap unbounded maximum value

**URL:** https://discuss.elastic.co/t/heatmap-unbounded-maximum-value/178699
**Category:** Kibana
**Created:** [April 26, 2019, 5:15pm UTC](https://discuss.elastic.co/t/heatmap-unbounded-maximum-value/178699 "2019-04-26T17:15:03Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Pure-AdamuKaapan](https://avatars.discourse-cdn.com/v4/letter/p/ea5d25/32.png) [@Pure-AdamuKaapan](https://discuss.elastic.co/u/Pure-AdamuKaapan)
#### Post date: [April 26, 2019, 5:15pm UTC](https://discuss.elastic.co/t/heatmap-unbounded-maximum-value/178699/1 "2019-04-26T17:15:03Z")

</div>

Hello! I'm currently working on creating a Kibana heatmap for visualizing latencies of multiple devices over time, but we're running into an issue with specifying a maximum value on the axis. Namely, the issue is that if a value is above the maximum we specified, it's simply empty. What would be ideal is creating an "unbounded" (if that's the right term) range, which is basically "anything greater than 5 milliseconds" for example. Our current solution is to simply make a range with an obscenely high end value, but that's not super aesthetically pleasing to look at and looks strange. I was wondering if anyone had insights on a way to do this, or if a code change would need to be made to support it?

Pictures:  
Current state without the very large range at the end: note that the top row is blank because the value is outside the range

 ![03%20AM](https://us1.discourse-cdn.com/elastic/original/3X/5/d/5d34762dd91a26e0acdb463a344e2d70e7c80cf2.png)

Current state if we make a very large range: note the ugly "999999" in the legend. It would be ideal for it to just be "5.000 - " with the second value blank to indicate unbounded.

 ![58%20AM](https://us1.discourse-cdn.com/elastic/original/3X/9/2/92523c22a2a6a135a3450f89446ef9fc983d5852.png)

---

<div class="post-metadata">

### 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, 10:15pm UTC](https://discuss.elastic.co/t/heatmap-unbounded-maximum-value/178699/2 "2019-04-26T22:15:33Z")

</div>

Using the "filters" aggregation, you can do something similar at the moment, but it's not nearly as easy to use as the "range" aggregation itself:

 ![31%20PM](https://us1.discourse-cdn.com/elastic/original/3X/2/5/2591f6b311e1666ebfed1606e649133e4dc5e651.png)

---

<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: [May 24, 2019, 10:15pm UTC](https://discuss.elastic.co/t/heatmap-unbounded-maximum-value/178699/3 "2019-05-24T22:15:35Z")

</div>

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