Key ; from ; to ; doccount – How to solve related issues

Average Read Time

2 Mins

Key ; from ; to ; doccount – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ; from ; to ; doccount ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: aggregations.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

     String key = entry.getKeyAsString();            // Ip range as key
    String fromAsString = entry.getFromAsString();  // Ip bucket from as a String
    String toAsString = entry.getToAsString();      // Ip bucket to as a String
    long docCount = entry.getDocCount();            // Doc count

    logger.info("key [{}]; from [{}]; to [{}]; doc_count [{}]"; key; fromAsString; toAsString; docCount);
}
--------------------------------------------------

This will basically produce for the first example:





 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content