ScriptedResult – How to solve related issues

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. 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 “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 a customized report like this:

Analyze your cluster