New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade from 1.02 to 1.1 - lost all callback settings #1214

SoMuchToGrok opened this Issue Jun 4, 2015 · 2 comments


None yet
3 participants

SoMuchToGrok commented Jun 4, 2015

Hey Team,

Just upgraded to 1.1 from 1.02. Lost all callback settings across all streams. Not sure if this is a bug, but I figure it's worth opening an issue about. Will update later with more info, on the road right now.


This comment has been minimized.

SoMuchToGrok commented Jun 4, 2015

Quick update - nothing strange in the logs from the initial startup after the upgrade, other than graylog complaining about using a deprecated mongodb conf call (which is now corrected on my end).

I have confirmed that all callbacks were missing, not just email (I use email and slack callbacks).

The callback receivers and alert configuration were still there, only thing missing was the actual callbacks themselves.

If you need more information, let me know. I've since recreated all of the callback settings and everything is back to normal.

@bernd bernd self-assigned this Jun 5, 2015

@bernd bernd added the bug label Jun 5, 2015

@bernd bernd added this to the 1.1.1 milestone Jun 5, 2015


This comment has been minimized.


bernd commented Jun 5, 2015

Thank you for the report! We found the issue and will provide a fix ASAP.

The problem is that the MongoDB collection name for alarmcallback configurations was called alarmcallbackconfigurations in 1.0 and got renamed to alarmcallbackconfiguration (missing s) by accident in 1.1.

@bernd bernd assigned dennisoelkers and unassigned bernd Jun 5, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment