How To Solve Issues Related to Log – Key ; point ; doccount

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Jan-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Key ; point ; doccount” it’s important to understand common problems related to Elasticsearch concepts: aggregations. See detailed explanations below complete with common problems, examples and useful tips.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Elasticsearch Deep aggregation doc count doesnt match 0.23 K 

2Show all Elasticsearch aggregation results 69.97 K  143


Log Context

Log ”Key [{}]; point {}; doc_count [{}]” classname is geohashgrid-aggregation.asciidoc
We have extracted the following from Elasticsearch source code to get an in-depth context :

 for (GeoHashGrid.Bucket entry : agg.getBuckets()) {
    String keyAsString = entry.getKeyAsString(); // key as String
    GeoPoint key = (GeoPoint) entry.getKey();    // key as geo point
    long docCount = entry.getDocCount();         // Doc count

    logger.info("key [{}]; point {}; doc_count [{}]"; keyAsString; key; docCount);
}
--------------------------------------------------

This will basically produce:







About Opster

Opster identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to prevent issues, optimize performance and save resources.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster