Project

General

Profile

Bug #3571

Message logger configuration

Added by Rob Kutschke over 6 years ago. Updated over 1 year ago.

Status:
Accepted
Priority:
Low
Assignee:
-
Category:
Infrastructure
Target version:
-
Start date:
Due date:
09/30/2013
% Done:

0%

Estimated time:
16.00 h
Occurs In:
Scope:
Internal
Experiment:
-
SSI Package:
messagefacility
Duration:

Description

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?


Related issues

Related to messagefacility - Feature #3270: Add maximum back-off parameter for "limit"?Accepted2013-09-30

Related to messagefacility - Feature #3271: Log a message indicating when a message type has been limitedAssigned2013-09-30

History

#1 Updated by Christopher Green almost 6 years ago

  • Due date set to 09/30/2013
  • Category set to Infrastructure
  • Target version set to 1.09.00
  • Start date deleted (03/07/2013)
  • 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.

#2 Updated by Christopher Green almost 6 years ago

  • Status changed from New to Accepted

#3 Updated by Christopher Green over 5 years ago

  • Target version changed from 1.09.00 to 521

#4 Updated by Kyle Knoepfel over 1 year ago

  • Target version deleted (521)


Also available in: Atom PDF