search

Graylog2 / graylog2-server

Free and open log management
https://www.graylog.org
Other
7.33k stars 1.06k forks source link

Upgrade to v1.1.1, no alerts triggering #1239

Closed SoMuchToGrok closed 9 years ago

SoMuchToGrok commented 9 years ago

Hey Team,

Upgraded to v1.1.1 after losing the mongodb alert callback settings. I had previously re-created all of the alert callback settings prior to the upgrade to v1.1.1 (at v1.1). Post upgrade, all callback settings stayed the same; as expected - no mongodb migration commands were run.

Since upgrading, no alerts are triggering. Streams are showing no triggered alerts in the past 3 days, but when I search within a stream itself, there are plenty of entries. The actual trigger mechanism seems to be broken/configured incorrectly. Has anything changed in regards to message count conditions? The below logic doesn't seem to be functional anymore.

"Alert is triggered when there are more than 0 messages in the last minute. Grace period: 0 minutes. Including last 10 messages in alert notification."

See attached image for alert conditions, callbacks, receivers, and triggered alerts.

graylog_callbacks

Thanks, Z

bernd commented 9 years ago

I just tried to reproduce this but it works fine for me.

stream-alerts

Can you show us the output of the following MongoDB commands?

db.streams.find().pretty()
db.alarmcallbackconfigurations.find().pretty()

You can also write an email with that if you cannot post that here. (bernd(at)graylog.com)

SoMuchToGrok commented 9 years ago

Email sent, thanks Bernd.

SoMuchToGrok commented 9 years ago

After upgrading to v1.1.2, this issue is no longer present.

joschi commented 9 years ago

Thanks for the update! I'm closing this issue, please feel free to add a comment if the problem comes up again.