I am not sure what I am doing wrong in getting the watcher to trigger. Each of the current three nodes has the JVM Heap Usage Pct over 25% (attached screenshot). The condition in the watcher is purposely set at > 5% to get a trigger. The aggregation basically return doc_count > 0 when the "node_stats.jvm.mem.heap_used_percent" is "gt" 5. Here is the gists for the Watcher, GET & RESPONSE:
Watcher:
GET & RESPONSE from aggregations:
Logs Result for condition met is false, result.condition.metfalse result.condition.statussuccess
can you share the output of the execute watch API or the watcher history? This will show the data that was retrieved and was executed against the watch condition - which should help to pinpoint the problem.
Thanks for pointing out the buckets was empty. Took out the field "types": [ "node_stats" ] and now the condition is met the bucket contain the three nodes heap jvm used pct. Not sure why taking out the field "types" would caused the condition to be met.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.