Open stefan328 opened 5 months ago
Hello there - how would I go about reproducing this?
Does this occur every time you navigate to Alerts --> Notifications?
Hello there - how would I go about reproducing this?
Does this occur every time you navigate to Alerts --> Notifications?
Yes everytime. Seems it only happens when Graylog was updated 5.2.7 -> 6.0.1 and there were notifications configured in old version
Hi @stefan328!
Could you provide the notification type(s) you have configured?
GET /api/events/notifications/paginated?page=1&per_page=20&sort=title&order=asc
Response: 500 {"type":"ApiError","message":"IOException encountered while parsing"}
@stefan328 thank you, but could you also provide which type or types of notifications you have configured in Graylog when this happens. E.x. Email Notification
, Slack Notification
etc.
If you could narrow it down it would help us troubleshoot which one is causing the error.
@stefan328 Hi, you still see this problem/have the mongodb that had that issue around? If yes, could you run db.getCollection("event_notifications").distinct('config.type')
in mongodb and post the results for me?
The exact error occurs when there is an event notification type string in mongodb that does not match one of the registered types. I think, in this situation, the FallbackNotificationConfig
should be used and work accordingly - but fails as one can see in the stack trace.
This error can be easily reproduced by creating an event notification and changing config.type
in mongodb to sth. that does clearly not exist. if you browse the list via the api, the error comes up in the server.log
Context
Your Environment