Graylog2 / Graylog2/graylog2-server

System Notification Events showing as disabled after adding a notification

Open
#19,655 0 comments 1 reaction 0 assignees View on GitHub
bug frontend triaged
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

## 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:

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.