How To Solve Issues Related to Log – Percent ; value

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 “Percent ; value” 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 Get Percentage of Values in Elasticsearch 4.75 K 3

2Percentage Of Documents That Have A  


Log Context

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

 // For each entry
for (Percentile entry : agg) {
    double percent = entry.getPercent();    // Percent
    double value = entry.getValue();        // Value

    logger.info("percent [{}]; value [{}]"; percent; value);
}
--------------------------------------------------


This will basically produce for the first example:






About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues.

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

Need help with any Elasticsearch issue ? Contact Opster