# Inconsistent content in data table visualization

**URL:** <https://discuss.elastic.co/t/inconsistent-content-in-data-table-visualization/177812>\
**Category:** Kibana\
**Created:** [April 22, 2019, 7:58am UTC](https://discuss.elastic.co/t/inconsistent-content-in-data-table-visualization/177812 "2019-04-22T07:58:22Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![zivklara](https://avatars.discourse-cdn.com/v4/letter/z/77aa72/32.png) [@zivklara](https://discuss.elastic.co/u/zivklara)\
**Post date:** [April 22, 2019, 7:58am UTC](https://discuss.elastic.co/t/inconsistent-content-in-data-table-visualization/177812/1 "2019-04-22T07:58:23Z")

</div>

Hi,  
I’m trying to work with data table visualization to show some error logs that occurred during tests I run, but I’m having problems with showing all the data.

Basically I need all my tables to be sorted by date (e2e\_test\_start\_time field), and that no row will be missing (if it exists, and fits my date range, it should be showing).

But the content is inconsistent, sometimes there are missing rows, and not all relevant data is shown.

For example,  
I set a 4-day date range: 2019-04-18 00:00:00.000 - 2019-04-21 23:59:59.999  
Order on e2e\_test\_start\_time field is set to Descending.  
There were many logs that occurred during this time, but it only shows 2 entries:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/e/fe9bc4fc8669be101eb42775614bef0ca37ecd97.png)

Same 4-day date range, I changed order to Ascending, no data at all (I would love to know why did this happen):

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/1/a180a6bed362c7ed617866b26667814b03a9294e.png)

Changing back to Descending, and changing the date range to a smaller one, 2 days range. Now I get more results:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/8/d8656bb11a7976aedcbc1b889e9092731ec40c37.png)

Please help me in understanding what am I doing wrong,

1. why is larger date range shows less data? (even though the limit is 200, and it only showed 2 entries)
2. how can I make it present a sorted data by date?

Thanks,  
Ziv

---

<div class="post-metadata">

**Author:** ![markov00](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markov00/32/33316_2.png) [@markov00](https://discuss.elastic.co/u/markov00)\
**Post date:** [April 29, 2019, 9:02am UTC](https://discuss.elastic.co/t/inconsistent-content-in-data-table-visualization/177812/2 "2019-04-29T09:02:51Z")

</div>

Hello @zivklara,  
thanks for your question.

This is a strange behaviour, but before filing an bug ticket I'd like to ask you few more question on that:

- on the first example (4 days, descend order, 200 size) have you tried to hit the refresh button on the right of the query bar? if so, can you please post here the `request` and `response` that are available on the inspector panel (top bar `inspect` -\> `View: requests`) (please remove any sensible data from that) I'd like to check if the inconsistence is on the query or on the visualization itself.

- can you flag `Group other values in separate bucket` and apply the changes to see if, at least, we can list the fact that we have other documents under the same time range?

Thanks for your patience  
Marco

---

<div class="post-metadata">

**Author:** ![zivklara](https://avatars.discourse-cdn.com/v4/letter/z/77aa72/32.png) [@zivklara](https://discuss.elastic.co/u/zivklara)\
**Post date:** [April 29, 2019, 10:26am UTC](https://discuss.elastic.co/t/inconsistent-content-in-data-table-visualization/177812/3 "2019-04-29T10:26:37Z")

</div>

Hi, thanks for the response 🙂

Regarding #2, I’ll have to check that later, and will update later today or tomorrow.  
But in the 3rd example, you can see documents that are in the range (April 19), that are not shown in the first example (range was April 18-21).

Now for #1, Error counter increases by 1 every time I mouse click (on Refresh, on the arrow near ‘Split Rows’ and anywhere on the screen):

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/b/0bf6c4a987678b61c07bd887bb2ad16a55c2125a.png)

Request and response from when I clicked on refresh (I hope that’s what you meant, if not, please let me know and I’ll try to get it right):

**Request:**  
POST /elasticsearch/\_msearch HTTP/1.1 Host: e2e-kibana Connection: keep-alive Content-Length: 1614 Accept: application/json, text/plain, _/_ Origin: [http://e2e-kibana](http://e2e-kibana) kbn-version: 6.5.2 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36 content-type: application/x-ndjson Referer: [http://e2e-kibana/app/kibana](http://e2e-kibana/app/kibana) Accept-Encoding: gzip, deflate Accept-Language: he-IL,he;q=0.9,en-US;q=0.8,en;q=0.7 Cookie: io=lzdVqfCvAPQ8HWFRAAAI

Parsed:  
Accept: application/json, text/plain, _/_  
Accept-Encoding: gzip, deflate  
Accept-Language: he-IL,he;q=0.9,en-US;q=0.8,en;q=0.7  
Connection: keep-alive  
Content-Length: 1614  
content-type: application/x-ndjson  
Cookie: io=lzdVqfCvAPQ8HWFRAAAI  
Host: e2e-kibana  
kbn-version: 6.5.2  
Origin: [http://e2e-kibana](http://e2e-kibana)  
Referer: [http://e2e-kibana/app/kibana](http://e2e-kibana/app/kibana)  
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36

**Response:**  
HTTP/1.1 200 OK warning: 299 Elasticsearch-6.5.1-8c58350 "Deprecated field [inline] used, expected [source] instead" "Mon, 29 Apr 2019 10:15:20 GMT", 299 Elasticsearch-6.5.1-8c58350 "Deprecated field [valueType] used, expected [value\_type] instead" "Mon, 29 Apr 2019 10:15:20 GMT", 299 Elasticsearch-6.5.1-8c58350 "returning default values for missing document values is deprecated. Set system property '-Des.scripting.exception\_for\_missing\_value=true' to make behaviour compatible with future major versions!" "Mon, 29 Apr 2019 10:15:20 GMT" content-type: application/json; charset=UTF-8 kbn-name: kibana kbn-xpack-sig: c27be63268dc2af63250e0931086a350 cache-control: no-cache vary: accept-encoding content-encoding: gzip connection: close Date: Mon, 29 Apr 2019 10:15:20 GMT Transfer-Encoding: chunked

Parsed:  
cache-control: no-cache  
connection: close  
content-encoding: gzip  
content-type: application/json; charset=UTF-8  
Date: Mon, 29 Apr 2019 10:15:20 GMT  
kbn-name: kibana  
kbn-xpack-sig: c27be63268dc2af63250e0931086a350  
Transfer-Encoding: chunked  
vary: accept-encoding  
warning: 299 Elasticsearch-6.5.1-8c58350 "Deprecated field [inline] used, expected [source] instead" "Mon, 29 Apr 2019 10:15:20 GMT", 299 Elasticsearch-6.5.1-8c58350 "Deprecated field [valueType] used, expected [value\_type] instead" "Mon, 29 Apr 2019 10:15:20 GMT", 299 Elasticsearch-6.5.1-8c58350 "returning default values for missing document values is deprecated. Set system property '-Des.scripting.exception\_for\_missing\_value=true' to make behaviour compatible with future major versions!" "Mon, 29 Apr 2019 10:15:20 GMT"

---

<div class="post-metadata">

**Author:** ![markov00](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markov00/32/33316_2.png) [@markov00](https://discuss.elastic.co/u/markov00)\
**Post date:** [April 29, 2019, 10:37am UTC](https://discuss.elastic.co/t/inconsistent-content-in-data-table-visualization/177812/4 "2019-04-29T10:37:17Z")

</div>

Thanks,  
for the request and response I mean a different Kibana feature. You can find a query inspector on the top bar of your Kibana app, in red on this screenshot:

 ![0bf6c4a987678b61c07bd887bb2ad16a55c2125a](https://us1.discourse-cdn.com/elastic/original/3X/2/c/2c98ef5811e2895ecad098eff5c3fe04fdfa35b0.png)

Regarding the error, just as a test, could you please disable all the chrome extension you have? seems to be something caused by that, but I'm just triaging the root cause. Thanks

---

<div class="post-metadata">

**Author:** ![zivklara](https://avatars.discourse-cdn.com/v4/letter/z/77aa72/32.png) [@zivklara](https://discuss.elastic.co/u/zivklara)\
**Post date:** [May 2, 2019, 2:24pm UTC](https://discuss.elastic.co/t/inconsistent-content-in-data-table-visualization/177812/5 "2019-05-02T14:24:03Z")

</div>

Ok, I think I got it right this time...

- response is around 4000 lines, and i don't see an option to upload a file in here, so i'm adding here links to downloading request and response files:  
**request:** [https://ufile.io/kp3jmj27](https://ufile.io/kp3jmj27)  
**response:** [https://ufile.io/6j7iwl46](https://ufile.io/6j7iwl46)

- I flagged 'Group other values...', and then I got more lines, but with 'Other' instead of date:  

- Regarding the errors, I disabled all of my extensions (except one where the option to disable is disabled), and I still got those errors on every mouse click I made.

Thanks

---

<div class="post-metadata">

**Author:** ![markov00](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markov00/32/33316_2.png) [@markov00](https://discuss.elastic.co/u/markov00)\
**Post date:** [May 3, 2019, 10:31am UTC](https://discuss.elastic.co/t/inconsistent-content-in-data-table-visualization/177812/6 "2019-05-03T10:31:47Z")

</div>

So the response seems fine, so this should be an issue on Kibana. I will take a look at the existing issues and see of there is any. I will try to test it with the same data also on my end.

Thanks

---

<div class="post-metadata">

**Author:** ![zivklara](https://avatars.discourse-cdn.com/v4/letter/z/77aa72/32.png) [@zivklara](https://discuss.elastic.co/u/zivklara)\
**Post date:** [May 20, 2019, 10:57am UTC](https://discuss.elastic.co/t/inconsistent-content-in-data-table-visualization/177812/7 "2019-05-20T10:57:01Z")

</div>

Hi, did you find the root cause? is it really a bug, or another issue?

---

<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 17, 2019, 10:57am UTC](https://discuss.elastic.co/t/inconsistent-content-in-data-table-visualization/177812/8 "2019-06-17T10:57:04Z")

</div>

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