console spam mitigation
Racer1
Join Date: 2002-11-22 Member: 9615Members
Join Date: 2002-11-22 Member: 9615Members
Every so often a game console message gets spammed continuously in-game. While this is helpful information that can point to a script/game bug, at a certain point it becomes a unnecessary duplication. I'd like to see a very simple console spam limiter get added to ns2.
As messages are displayed, the logger could keep a copy of the 10? most recent distinct console messages, with an associated counter for each. If a specific log message is repeated more than 20? times before getting replaced, it would be placed in a special "spam console message" list. This fact would be logged and from that point on, any occurrence of that log message would be ignored.
As this process could have a potential performance impact, a console message counter could be implemented which would simply count console messages. (This would cause negligible performance impact). If the count exceeded a threshold, THEN the above process would be enabled. The counter would reset every 2 minutes (and the counter threshold would be based on a typical 5 minute message count). However, once the threshold is reached, log mitigation would be enabled until the next round begins.
As messages are displayed, the logger could keep a copy of the 10? most recent distinct console messages, with an associated counter for each. If a specific log message is repeated more than 20? times before getting replaced, it would be placed in a special "spam console message" list. This fact would be logged and from that point on, any occurrence of that log message would be ignored.
As this process could have a potential performance impact, a console message counter could be implemented which would simply count console messages. (This would cause negligible performance impact). If the count exceeded a threshold, THEN the above process would be enabled. The counter would reset every 2 minutes (and the counter threshold would be based on a typical 5 minute message count). However, once the threshold is reached, log mitigation would be enabled until the next round begins.
Comments
Instead of
missing richochet
missing richochet
missing richochet
missing richochet
It is
missing richochet(4)
Would make things more organized.