How can i see Packet loss per IP or domain

[MatejsLab]

Hi

Now i am surprised that yesterday i had zero packet loss on chart, but today it is all the time around 1to 5% on netstat chart, which looks severe.

How do i know what test website isnt repllying, as it shows like internet is bad, but i suspect that one of the test websites is iffy as its saturday.

How can i confirm that there is no severe issue with my internet, as UptimeKuma says 100% to google and synology servers, and my internet experience today is fine.

Hwo can i display metrics per IP or domain of monitors for packet loss, so i can know the cause.

Thanks, Matej

[plaintextpackets]

Unfortunately as it's written now the packet loss from all of the anchors is aggregated before it gets sent to prometheus / grafana. What you could do temporarily is a Wireshark capture to look at which ICMP pings are failing consistently.

[MatejsLab]

Indeed there are internet issues, otherwise i wouldn't need netprobe lite. Many are droping.

I directed my router to 4G backup and packet loss went to 0% and stays there for long time, so my fiber optics ISP or modem actually may have an issue that is intermitent, but today it was obvious, as connecting back to fiber packet loss comes back. I had fiber and 4G on failover, The annoyance is that even loadbalancing both connections on Unifi doesnt solve an issue. Only full switchover to my 4G backup is great when there is no peak hours.

I may have to call on Telekom or T2 and tell them they have to solve this. The fiber is leased from Telekom and we have T2, before we had Telemach over same Telekom fiber, therefore issues persist.

Telemach the previous ISP they said it is normal, I may have to do periodic traceroute to pinpoint them the problematic node?

Thanks for guidance, the tool is indeed usefull.

Matej

V sob., 27. apr. 2024, 17:27 je oseba plaintextpackets < @.***> napisala:

Unfortunately as it's written now the packet loss from all of the anchors is aggregated before it gets sent to prometheus / grafana. What you could do temporarily is a Wireshark capture to look at which ICMP pings are failing consistently.

— Reply to this email directly, view it on GitHub https://github.com/plaintextpackets/netprobe_lite/issues/14#issuecomment-2080903384, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG3CQWJV63JYKOUOEP7ZASDY7O7VNAVCNFSM6AAAAABG37VAXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQHEYDGMZYGQ . You are receiving this because you authored the thread.Message ID: @.***>

[plaintextpackets]

I'm working on a version that lets you break out the packet loss, latency and jitter by destination:

I should have this ready soon

[plaintextpackets]

https://github.com/plaintextpackets/netprobe_lite/tree/separate_metrics

If you'd like to test before it is merged

[plaintextpackets]

Fixed with https://github.com/plaintextpackets/netprobe_lite/pull/20