[MXS-4300] Make log_throttling smarter Created: 2022-09-19 Updated: 2023-09-29 Resolved: 2023-09-29 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 6.4.11, 22.08.9, 23.02.5, 23.08.2 |
| Type: | Task | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
The log throttling functionality is currently triggered when 10 identical messages (generated by the same line of code in the source) are logged which suppresses the message for 10 seconds. After the 10 seconds, the same log messages are logged again 10 times until the suppression is triggered again. A better approach would be to be more aggressive in the suppression and keep suppressing the messages until no messages are logged during the suppression period. The total count of suppressed messages could be logged when the suppression period is over. |
| Comments |
| Comment by Johan Wikman [ 2022-09-21 ] |
|
The throttling was introduced to prevent over-zealous logging from flooding the log, but whenever the throttling filter has kicked in, the logging behaviour of MaxScale in that particular context should be reviewed and tuned. Eventually, the throttling should never kick in, as the logging is done in such a manner that flooding never occurs. |