Open Kn-ut99 opened 3 years ago
This seems to be a bug with the legacy plugin support, I'll leave this open because probably others will run into the same thing and it should be fixed as long as we support the legacy ones.
In the meantime, we will have direct support for Mattermost soon: https://github.com/Graylog2/graylog-plugin-integrations/pull/839 (if merged in time, it should be part of the next bugfix release and in 4.1 for sure).
When a Notification is set on an Event Definition, an error "Something went wrong" is displayed when viewing the Event Definition.
Expected Behavior
When clicking on the name of an Event Definition, a page is displaying the current configuration of the Event Definition.
Current Behavior
On the Event Definition that use a specific Notification (Legacy callback, for Mattermost), Graylog throws an error when clicking on the Event Definition title, thus preventing the display of its current configuration and preventing the alert to be correctly published to Mattermost
Possible Solution
Remove the Notification from the Event Definition.
Steps to Reproduce (for bugs)
legacy-alarm-callback-notification-v1
(Legacy Alarm Callbacks / Legacy Slack Alarm Callback) notification with default settingsContext
I'm trying to publish our alerts in Mattermost and the only notification settings I found to be working (via the
Execute test notification
button) is the one described above : Legacy Alarm Callbacks / Legacy Slack Alarm Callback. However this does trigger the bug explained here and alert notifications are not published in Mattermost.Your Environment