ScriptedResult – How to solve related issues

Average Read Time

2 Mins

ScriptedResult – 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 ” ScriptedResult ” 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 “ScriptedResult [{}]” classname is scripted-metric-aggregation.asciidoc.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 [source;java]
--------------------------------------------------
// sr is here your SearchResponse object
ScriptedMetric agg = sr.getAggregations().get("agg");
Object scriptedResult = agg.aggregation();
logger.info("scriptedResult [{}]"; scriptedResult);
--------------------------------------------------

Note that the result depends on the script you built.
For the first example; this will basically produce:





 

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

Analyze your cluster