Red Hat Bugzilla – Bug 875375
Event log - a method to bypass flood filtering
Last modified: 2016-02-10 14:29:58 EST
Currently we filter event log per message type.
If we have two DIFFERENT warnings or two DIFFERENT errors produced at same time (more or less), one gets filtered.
These errors or warnings may be important so blindly filter is not something that should be done.
1. Filter based on message type and message text.
2. Add some unique id to messages that must not be filtered. This unique id will be modified by producer for every message that must bypass filtering.
can you please give a concerete example/use case?
(I'm guessing this is related to warning from bootstrap...)
(In reply to comment #1)
> can you please give a concerete example/use case?
> (I'm guessing this is related to warning from bootstrap...)
Bootstrap infos, warnings, errors messages are sent via generic log types of info, warning, error.
Warnings and errors that received from host, such as approving gpg key, manual intervention action or errors should be displayed for user to see and act.
Infos can be filtered at will.
Modified, per test-case is not correct with current message definition.
What important is that warnings are not lost now.
I suggest closing this.
3.2 has been released