Stream alerts no longer firing after upgrade to 2.0 #2169
Comments
|
To clarify - adding a new message count condition says "than 1 messages in the last 3 minute and " editing the existing one says "than 1 message in the last 3 messages and" ... |
|
Fixed the wording glitch. I am not able to reproduce non-firing stream alerts. Is the stream paused? Do you see new stream alerts being added to the list at the bottom of the "Manage Alerts" page? |
|
No, streams is active and receiving messages. I just deleted & recreated the alert conditions and now alerts are firing again ... I had to do this for several streams ... |
|
Do you have a backup of your MongoDB before you recreated the stream alert conditions? It would really help if you could extract one that is not working, so we can investigate what's causing this. |
|
No - unfortunately not .... |
|
Same for me after upgrading to 2.0 streams alerts didn't work. No mongodb backup... |
|
Do you see anything in your server logs? |
|
I'm also experiencing this issue. Is there anything specific you want from my MongoDB? |
In 1.3.x numerical alert condition parameters were stored by MongoDB (resp. the mongo java driver) in a way, that they are returned as Doubles to the server, while alert conditions persisted in 2.0.0 return numerical parameters as Integer. Therefore, 2.0.0 cannot handle alert conditions stored in 1.3.x, so legacy installations upgraded to 2.0.0 do not check any alert conditions anymore. This change allows to handle both formats by generally assuming they are Number/Double types and returning their `intValue()`. Fixes #2169
In 1.3.x numerical alert condition parameters were stored by MongoDB (resp. the mongo java driver) in a way, that they are returned as Doubles to the server, while alert conditions persisted in 2.0.0 return numerical parameters as Integer. Therefore, 2.0.0 cannot handle alert conditions stored in 1.3.x, so legacy installations upgraded to 2.0.0 do not check any alert conditions anymore. This change allows to handle both formats by generally assuming they are Number/Double types and returning their `intValue()`. Fixes #2169
In 1.3.x numerical alert condition parameters were stored by MongoDB (resp. the Mongo Java Driver) in a way, that they are returned as Double while alert conditions persisted in 2.0.0 return numerical parameters as Integer. Therefore, 2.0.0 cannot handle alert conditions stored in 1.3.x and legacy installations upgraded to 2.0.0 do not check any alert conditions anymore. This change allows to handle both formats by generally assuming they are Number/Double types and returning their `intValue()`. Fixes #2169
|
This has been fixed and the fix will be included in 2.0.1. Thanks for helping, everybody! |
|
Problem still persists after upgrading to 2.0.1. I tried re-creating the alert conditions for the streams but still no luck. Is there any script that needs to be run to get it working again? I considered that it may be a problem with the notifier, but the "Triggered alerts" section on the stream configuration page also says "This stream has never triggered an alert." even though there are many messages in the stream that should have triggered the alert. The current configuration is: Should I open a new issue? |
Problem description
Stream alerts are no longer firing after upgrading to 2.0 even though the stream receives messages.
The Message count condition :
Alert is triggered when there is more than one message in the last 3 minutes. Grace period: 0 minutes. Including last message in alert notification.
The above worked just fine in 1.3 but apparently no longer works in 2.0 - no alerts have been generated since upgrading.
There is a discrepancy between editing the existing message count condition and adding a new one which I cannot explain :
The text was updated successfully, but these errors were encountered: