question about health_monitor's "prune" processing

Ning Fu

Hi, folks:

Recently I am reading health_monitor code, and I am confused about
"prune" processing -- it seems that there is an intent to remove the events
that are obsoleted from the waiting queue:

But it looks like that the event list is never used as the sending queue:

An event is just passed to the plugin directly.

If my understanding is correct, then what's the purpose of this call at
@processor.enable_pruning(Bhm.intervals.prune_events) ?


Join { to automatically receive all group messages.