AlertQuartz.Consumer#consumer 方法条件判断会出现问题

[zhiyuan192shine]

if (lag > alarmConsumer.getLag() && alarmConsumer.getAlarmTimes() <= alarmConsumer.getAlarmMaxTimes()) {
    // alarm consumer
    alarmConsumer.setAlarmTimes(alarmConsumer.getAlarmTimes() + 1);
    alarmConsumer.setIsNormal("N");
    alertService.modifyConsumerStatusAlertById(alarmConsumer);
    try {
        sendAlarmConsumerError(alarmConfing, alarmConsumer, lag);
    } catch (Exception e) {
        LOG.error("Send alarm consumer exception has error, msg is " + e.getCause().getMessage());
    }
} else {
    if (alarmConsumer.getIsNormal().equals("N")) {
        alarmConsumer.setIsNormal("Y");
        // clear error alarm and reset
        alarmConsumer.setAlarmTimes(0);
        // notify the cancel of the alarm
        alertService.modifyConsumerStatusAlertById(alarmConsumer);
        try {
            sendAlarmConsumerNormal(alarmConfing, alarmConsumer, lag);
        } catch (Exception e) {
            LOG.error("Send alarm consumer normal has error, msg is " + e.getCause().getMessage());
        }
    }
}

alarmConsumer.getAlarmTimes() <= alarmConsumer.getAlarmMaxTimes() 不需要 = ， 只需要 < 就行，否会导致 else 代码块执行，出现 lag > lag_threshold 情况仍会被正常告警

[smartloli]

OK, Fixed this bug in the next release.

[smartloli]

fixed by v1.4.1