Log Id . _source – How To Solve Related Issues



Log Id . _source – How To Solve Related Issues

Opster Team

Feb-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 causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Id . _source” 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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”-> id [{}]; _source [{}]” classname is tophits-aggregation.asciidoc
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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

    // We ask for top_hits for each bucket
    TopHits topHits = entry.getAggregations().get("top");
    for (SearchHit hit : topHits.getHits().getHits()) {
        logger.info(" -> id [{}]; _source [{}]"; hit.getId(); hit.getSourceAsString());
    }
}
--------------------------------------------------

This will basically produce for the first example:




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 How To Include The Id Field In The  

Official Document Question  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now