search

MetPX / sarracenia

https://MetPX.github.io/sarracenia
GNU General Public License v2.0
46 stars 22 forks source link

sr3 status messages/second is almost always 0 #1301

Open petersilva opened 1 day ago

petersilva commented 1 day ago 
host% sr3 status sender/wxo-op-be-dd04
status:
Component/Config                            Processes   Connection        Lag                              Rates
                                            State   Run Retry  msg data   Que   LagMax   LagAvg     Last  %rej     pubsub   messages     RxData     TxData
                                            -----   --- -----  --- ----   ---   ------   ------     ----  ----     ------   --------     ------     ------
sender/wxo-op-be-dd04                       lag     3/3     2 100%  13%     0     3d4h   23m15s   14.41s  0.0%     614B/s       0m/s       0B/s   6.0KiB/s

I see a lot of senders on this busy configuration, and pubsub messages rate... um... I feel like it should be higher than 0 message/second... it seems odd.

Actually... and entire status with dozens of configs, and they all show 0 message/second...

petersilva commented 1 day ago

philosophical question... if you have most components... they will receive a message, and then post a corresponding one for the next component... so for each file... there will be two messages... should we add the subscriber messages and posted messages together to get the message rate? or just use the higher of the two?

petersilva commented 1 day ago

wondering about changing time denominator to deal with lower rates of flow /s (second) -> /m (x60 per minute) -> /h (per hour *3600) but I think the stats reset every few minutes so likely /m is the most we can easily do.