Mismatch between Kibana totals and direct _msearch totals Elasticsearch 7.3.0

[jimmymacGA (James)]

I am having an issue with geospatial queries in Kibana returning different results that a direct _msearch query.

I copied the query params from the developer tools and posted it directly to my ElasticSearch server in Postman. I copied the URL as is and the query as is and the aggregations are different.

The number shards is the same and no failed shards are reported and the query runs successfully. And for development there is just one server so there are no variations.

What could be the reason for this ?

[warkolm (Mark Walkom)]

Can you post the queries you are using and the start of the responses.

Please format your code/logs/config using the </> button, or markdown style back ticks. It helps to make things easy to read which helps us help you

[Nathan_Reese]

Are you using Elastic maps or coordinate/region map visualization?

[jimmymacGA (James)]

`This is the query portion from the _msearch query in kibana

{"aggs":{"2":{"geohash_grid":{"field":"location","precision":2},"aggs":{"3":{"geo_centroid":{"field":"location"}}}}},"size":0,"_source":{"excludes":},"stored_fields":["*"],"script_fields":{},"docvalue_fields":[{"field":"@timestamp","format":"date_time"},{"field":"receiveddatetime","format":"date_time"}],"query":{"bool":{"must":[{"range":{"@timestamp":{"format":"strict_date_optional_time","gte":"2019-03-20T01:32:34.798Z","lte":"2020-03-20T01:32:34.798Z"}}}],"filter":[{"match_all":{}}],"should":,"must_not":}},"timeout":"30000ms"}

[jimmymacGA (James)]

No but I am using a geohash visualizuation in Kibana.