Log Key ; date ; doccount – How To Solve Related Issues


Log Key ; date ; doccount – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Key ; date ; doccount ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: aggregations.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “Key [{}]; date [{}]; doc_count [{}]” classname is datehistogram-aggregation.asciidoc
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 for (Histogram.Bucket entry : agg.getBuckets()) {
    DateTime key = (DateTime) entry.getKey();    // Key
    String keyAsString = entry.getKeyAsString(); // Key as String
    long docCount = entry.getDocCount();         // Doc count

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

This will basically produce for the first example:





 

Optimize Elasticsearch Performance

Try The Tool