Heatmap visualization issues

[ajoliveira]

Kibana version: 5.5.1

Elasticsearch version: 5.5.1

Server OS version: MacOS Sierra - 10.12.6

Browser version: Chrome - Version 60.0.3112.78 (Official Build) (64-bit)

Browser OS version: MacOS Sierra - 10.12.6

Original install method (e.g. download page, yum, from source, etc.): download

Description of the problem including expected versus actual behavior: Heatmap visualization has a number of display issues depending on values chosen for the intervals and min/max bounds.

Steps to reproduce:

1. Sample mapping and data (_bulk) - xy_test_heatmap.json.txt
2. Create heatmap, metric = count, aggregations on x and y values, intervals of 0.001, 0.002, etc.
3. Some behaviors noted:

• y-axis values out of order (reported in Sort sub-aggregation axis by term not working #10648) if it is not the first aggregation

- correct ordering if it is first aggregation

- missing some empty buckets even if options are selected but no min/max values specified

- depending on intervals specified (0.001 vs. 0.002), some y-axis values are missing (ex: -0.006)

- and also missing some empty buckets (combination of both)

- specifying min/max values and show empty buckets appears to work as desired (but forces you to specify min/max which you may not know, etc.)

- another variation, duplicated x-axis value of -0.006 (and missing/empty 0 count buckets?)

Errors in browser console (if relevant): none

Provide logs and/or server output (if relevant):

[ThomasYanghan]

Same problem to me. Actually in my situation, the missing value is not 0. Most time the missing value is a less smaller number and kibana did not respond that to me.

[nandanosql]

Same problem to me.
Kibana Version :- 6.3.1
Data is missing in few places but in ES index data is available.

[stratoula]

Let's evaluate this when we change the implementation to use elastic-charts instead

[flash1293]

Blocked on #103633

[flash1293]

All these things are solved in the Lens heatmap in 8.2:

No missing buckets and order of histograms doesn't matter

In case zeros should be spelled out, there's a dedicated setting for that: