Feature: Allow to disable/enable events

[cdprete]

Enhancement
Hello.

It would be great if, on a client-basis (e.g.: through metadata or so) as well as globally in the server configuration (of course, the client-basis configuration has higher priority over the global one), it would be possible to disable/enable (based on the configuration) the events displayed in the journal.

In my specific use case, I'm not really interested in getting flooded by INFO_UPDATED events since the info will always be updated because of the process information contained in its payload.
Therefore, I would like to have in the journal only the entries which really make sense (especially because of #4389).
But, it would make sense to generalize the feature and allow every event type to be enabled/disabled.

In the documentation I can see some configurations in this regard, but none that allows really to disable/enable them.

If it's too complicated or time consuming, it would be great to have at least the possibility to disable/enable them globally as part of the server configuration.

Kind regards and thanks in advance.

[SteKoe]

Hi @cdprete,

what about a filtering option in the journal view UI to hide specific event types? We are reluctant to add a filter mechanism in the backend but are willing to add some kind of filtering in the UI. What do you think? Would that fit your needs?

Redards.

[cdprete]

Hi @SteKoe

That option should already be covered with #4340.

If filtering on the backend is not an option (even though I can't really understand why), would it be possible to have a configuration flag to enable/disable the InfoUpdater job itself?
In this way the job wouldn't be in the context and, as side effect, I would be getting only status updates in the journal.