-
Notifications
You must be signed in to change notification settings - Fork 19
Missing 'loss' field in pingbeat output #28
Comments
Hi @zach929, this field should still be there. Rather than adding |
Hi @joshuar , thanks for the reply. The 'loss: true' event was not generated in 5.4 during my test. following is the pingbeat.yml:
Following is the output of the program:
100.100.100.100 is an obvious non-pingable address. In the output, only the 8.8.8.8 address generates ping event. The 'loss: true' event was not generated for '100.100.100.100'. |
Hi @zach929 okay, the loss processing is still there, but some refactoring of the code meant that some "loss" conditions were no longer being recorded. With 4f9c249:
The default timeout is relatively low, (10 x interval) simply because I originally want to keep the memory usage low where a large number of targets was defined and a low interval was being used. This Can you try the master branch and see if it is better? |
hi @joshuar, can you build a dev-release? I'm getting no 'loss: true' with the latest-Version |
i'm getting a lot of errors for unreachable hosts with the latest release
|
I'm also experiencing a continuous stream of 'ERR Couldn't read from connection: read ip4 0.0.0.0: i/o timeout' when an IP is unreachable - it filled up 7 log files in a second. Running at release v5.4.0 |
@atomicom @jegade @zach929 looks like I really made a mess of that last release. Can you try 5.4.1: https://github.com/joshuar/pingbeat/releases/tag/v5.4.1 This should fix both tracking of loss and also stop any unnecessary error messages. |
@joshuar much better, now the losts are tracked. Thank you |
in 1.0-beta, there is a 'loss:boolean' field that can capture packet loss. It seems this field is no longer present with 5.4.
This field is quite useful when detecting network instability. Could this field be added back?
The text was updated successfully, but these errors were encountered: