Project

General

Profile

Feature #3271

Log a message indicating when a message type has been limited

Added by Peter Shanahan over 6 years ago. Updated almost 2 years ago.

Status:
Assigned
Priority:
High
Assignee:
Target version:
-
Start date:
Due date:
09/30/2013
% Done:

0%

Estimated time:
2.00 h
Duration:

Description

I don't think this exists...

Can MF automatically generate a message when a given message type starts being throttled by limit?

E.g., category "Update" has a limit of 5, so we would have something like

MyApp: Update 1
MyApp: Update 2
MyApp: Update 3
MyApp: Update 4
MyApp: Update 5
MessageFacility: Msg-i Throttle "MyApp: Category 'Update' has been limited"
MyApp: Update 10
etc...

And, maybe, if timespan was set, when the timespan was hit
MessageFacility: Msg-i Throttle "MyApp: Category 'Update' limit reset"

Please due date with a grain of salt.

simple_example.cc (7.47 KB) simple_example.cc Ron Rechenmacher, 11/07/2017 01:08 PM

Related issues

Related to art - Bug #3571: Message logger configurationAccepted2013-09-30

History

#1 Updated by Christopher Green about 6 years ago

  • Due date changed from 01/31/2013 to 09/30/2013
  • Status changed from New to Accepted
  • Assignee deleted (Qiming Lu)
  • Target version set to 1.09.00
  • Start date deleted (01/12/2013)
  • Estimated time set to 2.00 h

This may reasonably be done as a drive-by as part of the implementation of issue #3571.

#2 Updated by Christopher Green over 5 years ago

  • Target version changed from 1.09.00 to 521

#3 Updated by Kyle Knoepfel almost 2 years ago

  • Target version deleted (521)

#4 Updated by Ron Rechenmacher almost 2 years ago

  • Priority changed from Normal to High

I would like to see this feature implemented.
Silently dropping log messages is usually not good, IMHO.
Additionally, (perhaps assuming no exponential back-off), a message should/could be added after the
limiting (associated with the first non-limited message) that indicates how many messages have
be limited/dropped.

#5 Updated by Christopher Green almost 2 years ago

Minor note: the end-of-execution summary should always tell you how many times a message was issued, not how many times it was printed.

#6 Updated by Kyle Knoepfel almost 2 years ago

  • Status changed from Accepted to Feedback

Message statistics, which include the number of times messages from a given category were logged or printed, can be displayed by setting the outputStatistics configuration parameter to true for any given destination.

Implementing the above feature is straightforward, the question is whether such a feature should be scheduled soon, due to our current demands implementing multi-threaded art. Please let us know urgent this feature is.

#7 Updated by Ron Rechenmacher almost 2 years ago

Sorry I didn't notice this earlier.
It doesn't seem to be too urgent in the grand scheme as another issue I just filed is higher priority.
I can't seem to get the statistics to print.
I've tried:
debugModules : ["*"]
destinations : {
xxx: {
type:cout
format:{wantSomeContext:false}
threshold:DEBUG
categories:{default:{limit:4 timespan:1 reportEvery:2}}
outputStatistics:true
resetStatistics:false
}
}

But this does not seem to work.
I'll attach an example program

#8 Updated by Kyle Knoepfel almost 2 years ago

  • Status changed from Feedback to Assigned
  • Assignee set to Paul Russo


Also available in: Atom PDF