Message logger configuration
This has been bugging me for a long time so I guess that it is time to write it down. As best I can tell, the message logger does linear backoff, not exponential backoff. I think of exponential backoff as something like the following:
1, 2, 3, 4, 5, 11, 21, 31, 41, 51, 101, 201, 301, 401, 501, 1001, 2001, 3001, 4001, 5001, 10001, 20001 and so on.
Note that this algorithm has 2 parameters; well, if you think of the factor of 10 as implied, it has only one parameter. I have not thought what I want it to do if someone set that one parameter to a number bigger than 10. What the message logger actually does is:
1, 2, 52, 102, 152, 202, 552 and every 50 events forever.
If I drop the reportEvery value to 10 it repeats every 10 events. In a few thousand events it keeps printing every 10th and never enters a mode when it goes into every 100 or every 1000. Maybe this behaviour is already there and we just need to learn how to select it. Maybe not?
#1 Updated by Christopher Green about 7 years ago
- Due date set to 09/30/2013
- Category set to Infrastructure
- Target version set to 1.09.00
- Start date deleted (
- Estimated time set to 16.00 h
- Scope set to Internal
- Experiment - added
- SSI Package messagefacility added
We believe the behavior is as-designed, in that the limit is exponential also: 5 messages at one level, 25 at the next, 125 at the next, etc. We also stipulate that this is not what most people would want.