"site" in eagle means an isolated monitored namespace for certain tenant, like a monitored cluster or service.
After policy changes, alert engine cannot detect the it, and no new schedulestate is generated. Currently, i use a workaround way. Once i change the policy, i will post the rest request 'coordinator/build', and it works. (Reporter: qingwzhao)
EIP-4.2
Status
colour
Red
title
P1
Kafka Producer to async + batchSize, set acks = 1, and go through implementation of alert publisher which is too slow.
EIP-4.3
Status
colour
Red
title
P1
Fix wrong metric declaration in alert bolt, which reduce the performance of alert engine performance a lot.
EIP-4.4
Status
title
P3
Improve configuration: hide "metadata service host/port" and "metadata Service Context Path", just pass through code instead of configuration.
EIP-4.5
Status
colour
Grey
title
p3
Migrate alert engine metadata store to eagle configuration, current configuration is very confusing
EIP-4.6
Status
colour
Grey
title
p3
Collect topology metric during checking status, and visualize in topology monitor page