Network monitor

[Toothless]

Alrighty guys, help me out. I need a monitor to see if my server is dropping packets on the physical machine, and virtual machines. I have no idea on whats good so I'm hoping you guys know.

 

[Solaris17]

Telegraf > InfluxDB > Grafana

 

[Toothless]

Telegraf > InfluxDB > Grafana

View attachment 107478

Anything like that, that is free?

 

[Solaris17]

Thats all free. But it takes work. What kind of issues are you having? TBH monitoring probably isnt going to get you what you want. Your verbage is also a little off. Monitoring individual packets isnt really a thing. I mean you could tune your monitoring to do that I guess but you never get the answers you want.

Advanced corporate networks follow the same rules as home networks. Monitoring just helps show us what satellite office or box in a rack has an issue. the troubleshooting steps are generally the same.

 

[Toothless]

Thats all free. But it takes work. What kind of issues are you having? TBH monitoring probably isnt going to get you what you want. Your verbage is also a little off. Monitoring individual packets isnt really a thing. I mean you could tune your monitoring to do that I guess but you never get the answers you want.

Advanced corporate networks follow the same rules as home networks. Monitoring just helps show us what satellite office or box in a rack has an issue. the troubleshooting steps are generally the same.

Im looking for dropped packets. I run automated clients for a game in virtual machines and they keep getting disconnected and I'm trying to figure out why. The error out with no packages received so, yeah, that thing.

 

[Solaris17]

for small time stuff your going to want wireshark. but im warning you, networking tools generally are not easy to master.

Personally, to me going with my gut everytime packet loss is an issue

-firewall
-latency

generally in that order.

Just a warning, wireshark will probably tell you whats breaking if you learn to read it. but there is no network monitor solution that will highlight the problem in green and say "Fix this" this is going to be a bit more rough.

EDIT:: I personally like working in reverse. I would comb through articles and see what if any ports need to be opened and on what protocol TCP or UDP.

I would then make sure the gear experiencing issues are on static IPs so its easier for me to manage.
Then I would modify or doublecheck my firewall config as needed.

If that worked out just fine. I would make sure the underlying OS and application are upto date.
followed by making sure I didnt set odd QoS policies or random driver/NIC level settings.