-
Problem report
-
Resolution: Fixed
-
Minor
-
7.0.4
-
None
-
Prev.Sprint, S24-W42/43
-
1
When in received data:
{
"cluster_name": "stage",
"status": "yellow",
"timed_out": false,
"number_of_nodes": 1,
"number_of_data_nodes": 1,
"active_primary_shards": 16,
"active_shards": 16,
"relocating_shards": 0,
"initializing_shards": 0,
"unassigned_shards": 1,
"delayed_unassigned_shards": 0,
"number_of_pending_tasks": 0,
"number_of_in_flight_fetch": 0,
"task_max_waiting_in_queue_millis": 0,
"active_shards_percent_as_number": 94.11764705882352
}
we have "number_of_data_nodes" =1, it goes to item key "es.cluster.number_of_data_nodes", which in trigger expression (formatted):
(last(/Elasticsearch Cluster by HTTP/es.nodes.fs.total_in_bytes)-last(/Elasticsearch Cluster by HTTP/es.nodes.fs.available_in_bytes)) / (last(/Elasticsearch Cluster by HTTP/es.cluster.number_of_data_nodes)-1) > last(/Elasticsearch Cluster by HTTP/es.nodes.fs.available_in_bytes)
results in division by 0 and making the trigger being in unknown state.
Note - the template in description says: It works with both standalone and cluster instances.
