Skip to content
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

System Notification Events showing as disabled after adding a notification #19655

Open
patrickmann opened this issue Jun 17, 2024 · 0 comments
Open

Comments

@patrickmann
Copy link
Contributor

patrickmann commented Jun 17, 2024

Expected Behavior

The event definition for System Notification Events should always be enabled.
Adding/removing event notifications should not make any difference.

Current Behavior

System Notification Events is showing as disabled after adding a notification.

PUT events/definitions/{id} is being called by the frontend with the (wrong) default state of DISABLED.
The backend apparently does not perform any special case checking for System Notification Events, and it ends up being disabled.

The events are still being fired - but the UI showing it disabled is very confusing.
Workaround: It can be reset to enabled using bulk actions (which shouldn't really be supported for this event definition either).

We should probably backport this to 5.x

Possible Solution

We already modify the event definition form in the frontend for System Notification Events. Set the status to ENABLED in the PUT API call.

Your Environment

  • Graylog Version: 6.0.3
  • Java Version:
  • OpenSearch Version:
  • MongoDB Version:
  • Operating System:
  • Browser version:
@patrickmann patrickmann changed the title System Notification Events is disabled after adding a notification System Notification Events showing as disabled after adding a notification Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants