You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a Per Cluster Metrics Monitor in the OpenSearch Plugins tab, selecting "Nodes stats" as the request type and clicking on "Preview condition response" after setting the trigger results in a script_exception runtime error.
How can one reproduce the bug?
Steps to reproduce the behavior:
Go to OpenSearch Dashboards.
Navigate to the "Plugins" tab and click on "Create Monitor."
Select "Per Cluster Metrics Monitor" as the monitor type.
For the query request type, choose "Nodes stats."
Click on "Preview query" to check the query response.
Set a trigger and leave the "Trigger condition" as default.
Click on "Preview condition response."
See the script_exception runtime error.
What is the expected behavior?
The trigger condition preview should return a valid response without throwing a script_exception runtime error.
This error only occurs when trying to preview the trigger condition. Query preview works as expected, and the error appears during the preview of the trigger condition response.
The text was updated successfully, but these errors were encountered:
What is the bug?
When creating a Per Cluster Metrics Monitor in the OpenSearch Plugins tab, selecting "Nodes stats" as the request type and clicking on "Preview condition response" after setting the trigger results in a script_exception runtime error.
How can one reproduce the bug?
Steps to reproduce the behavior:
script_exception
runtime error.What is the expected behavior?
The trigger condition preview should return a valid response without throwing a
script_exception
runtime error.What is your host/environment?
Do you have any screenshots?
ctx.results[0].nodes.NODE_ID.jvm.mem.heap_used_percent > 60
Do you have any additional context?
This error only occurs when trying to preview the trigger condition. Query preview works as expected, and the error appears during the preview of the trigger condition response.
The text was updated successfully, but these errors were encountered: