Watcher payload possibly broken in master #36177
Description
This watch works in 6.5.1, but does not work on master. The key issue seems to be that iterating over aggregations is broken in master. The log output should contain a list of all matched bucket keys when it fires, but instead logs nothing in the space where the data should be.
Please see the watch linked above. I've included a sample Heartbeat event that triggers the watch below:
{
"_index": "heartbeat-6.5.0-2018.12.03",
"_type": "doc",
"_id": "3pfCdWcBzOHIWwLnTiHd",
"_version": 1,
"_score": null,
"_source": {
"@timestamp": "2018-12-03T20:28:46.472Z",
"resolve": {
"host": "www.elastic.co",
"ip": "151.101.194.217",
"rtt": {
"us": 1667
}
},
"tcp": {
"port": 443,
"rtt": {
"connect": {
"us": 6037
}
}
},
"tls": {
"certificate_not_valid_before": "2018-11-13T14:03:14.000Z",
"certificate_not_valid_after": "2019-10-12T00:32:18.000Z",
"rtt": {
"handshake": {
"us": 15432
}
}
},
"beat": {
"name": "avce.local",
"hostname": "avce.local",
"version": "6.5.0"
},
"host": {
"name": "avce.local",
"architecture": "x86_64",
"os": {
"platform": "darwin",
"version": "10.14.1",
"family": "darwin",
"build": "18B75"
}
},
"http": {
"url": "https://www.elastic.co",
"rtt": {
"write_request": {
"us": 46
},
"response_header": {
"us": 209424
},
"validate": {
"us": 209439
},
"content": {
"us": 14
},
"total": {
"us": 231018
}
},
"response": {
"status_code": 200
}
},
"monitor": {
"name": "http",
"type": "http",
"host": "www.elastic.co",
"ip": "151.101.194.217",
"duration": {
"us": 232856
},
"status": "up",
"scheme": "https",
"id": "http@https://www.elastic.co"
}
},
"fields": {
"tls.certificate_not_valid_after": [
"2019-10-12T00:32:18.000Z"
],
"tls.certificate_not_valid_before": [
"2018-11-13T14:03:14.000Z"
],
"@timestamp": [
"2018-12-03T20:28:46.472Z"
]
},
"sort": [
1543868926472
]
}