Display the actual error/stack trace in Groovy/Painless script in UI while creation of triggers in Extraction query based alerts. about alerting

[mihirsoni]

@abhijithshivaswamy Thanks for reporting an issue. This is definitely needed. We would love to get this improved for painless. I am moving this to backend so that we can track it there.

[lucaswin-amzn]

+1 from me, what would also be great is if we could somehow integrate this with how the Elasticsearch DSL currently updates and informs you what the available params are and highlights any syntax errors.

[seraphjiang]

one option is to render full response just when we run esquery wtith syntax via Dev Tools

an example response will be like below.

the script_stack is a list of message which could point to the code fragments has the issue

{
  "type" : "script_exception",
  "reason" : "compile error",
  "script_stack" : [
    "... [0].hits.total.value > 0\nctx.results[0].hits.total ...",
    "                             ^---- HERE"
  ],
  "script" : "ctx.results[0].hits.total.value > 0\nctx.results[0].hits.total.value > 0\nctx.results[0].hits.total.value > 0\n",
  "lang" : "painless",
  "caused_by" : {
    "type" : "illegal_argument_exception",
    "reason" : "unexpected token ['ctx'] was expecting one of [{<EOF>, ';'}]."
  }
}