Ticket #259 (new enhancement)

Opened 8 years ago

Last modified 8 years ago

wave_serverV and Statmgr send too many messages

Reported by: stefan Owned by: somebody
Priority: major Milestone:
Component: statmgr Version:
Keywords: Cc:

Description

I see 34 messages in the period of one minute emailed to me from statmgr thanks to wave_serverV. One message per minute is too many, but 34 per minute makes me feel that statmgr should have some option to queue up messages for a period of time, be it one minute for a warning system, or X number of minutes for a secondary system. (there were a total of 48 messages for this particular minute export_scn_actv and export generic_also contributed messages > once per min.)

Here are six of the 32 wsv messages that arrived at 8:42AM Eastern Time: ((UTC_Mon Mar 04 13:42:18 2013 734D7FSSEISMIC/export_generic missed msg(s) i159 m26 t19 in WAVE_RING

)) ((UTC_Mon Mar 04 13:42:21 2013 734D7FSSEISMIC/export_generic missed msg(s) i159 m26 t19 in WAVE_RING

)) ((UTC_Mon Mar 04 13:42:39 2013 734D7FSSEISMIC/wave_serverV saw sequence gap before i159 m26 t19 sq53 in WAVE_RING

)) ((UTC_Mon Mar 04 13:39:44 2013 734D7FSSEISMIC/wave_serverV saw sequence gap before i159 m26 t19 sq190 in WAVE_RING

)) ((UTC_Mon Mar 04 13:42:41 2013 734D7FSSEISMIC/wave_serverV saw sequence gap before i159 m3 t19 sq64 in WAVE_RING

)) ((UTC_Mon Mar 04 13:39:44 2013 734D7FSSEISMIC/wave_serverV saw sequence gap before i159 m26 t19 sq235 in WAVE_RING

))

Change History

comment:1 Changed 8 years ago by stefan

And for example, six identical messages like this within the same minute:

((UTC_Wed Mar 6 01:04:30 2013 sangabriel/export_generic missed msg(s) i255 m99 t19 in WAVE_RING

))

Note: See TracTickets for help on using tickets.