ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.
One of a set of tools we're offering as a way to say thank you for being a part of the community.
Solved
Looking for recommendations on Network Monitoring Tool? What is your favorite?
Posted on 2017-03-07
Hello EE,
We have alerts and ping loss notifications, but I'm looking for a network monitoring tool that can get more granular on
-congestion
-qos
-latency
-who, what, where is causing
What is your favorite?
We have alerts and ping loss notifications, but I'm looking for a network monitoring tool that can get more granular on
-congestion
-qos
-latency
-who, what, where is causing
What is your favorite?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
5 Comments
Wireshark,intermapper, microsoft system center, these will help to troubleshoot and prevent all of the above you mention
Paessler PRTG (https://www.paessler.com/prtg) is pretty good. I've used it quite a bit. It can do packet sniffing via mirrored ports on the switch, or using full-blown NetFlow and other proprietary flow protocols. There are add-ins that can do a lot of customer monitoring too.
SolarWinds is another one I've used a lot. It's a beast, but can do just about anything.
You did write "network monitoring" and not "protocol analyzing". They are different. Wireshark is the king of free protocol analyzers, and I love it. But it's really meant for real-time analytics of your packets and protocols. The capture files grow huge, pretty fast - so you typically use these only for a few moments and then analyze the results. Whereas "network monitoring" as you specified is continuous, 24/7. It monitors for packet loss, latency, "top talkers", "top connections" HTTP query/replies, SMTP responses, Windows services, and anything else you could possibly want.
On the free side, Nagios has been around for a few decades and has a HUGE following, which means a HUGE knowledge base. The downside is that it's a BEAST to setup. Once it's setup though it's pretty easy to manage... and did I mention FREE? I like its small footprint. You can install it on a tiny PC running a tiny OS with no graphics and almost zero attack surface area. Plus, even though it's primarily a Linux product, it's Windows-friendly and can use plugins to monitor almost anything Windows related. It has enormous how-to's on monitoring network equipment, routers, switches, etc. Highly customizable; you can create complex notification schedules, targets, dependencies, etc.
Cheers,
SolarWinds is another one I've used a lot. It's a beast, but can do just about anything.
You did write "network monitoring" and not "protocol analyzing". They are different. Wireshark is the king of free protocol analyzers, and I love it. But it's really meant for real-time analytics of your packets and protocols. The capture files grow huge, pretty fast - so you typically use these only for a few moments and then analyze the results. Whereas "network monitoring" as you specified is continuous, 24/7. It monitors for packet loss, latency, "top talkers", "top connections" HTTP query/replies, SMTP responses, Windows services, and anything else you could possibly want.
On the free side, Nagios has been around for a few decades and has a HUGE following, which means a HUGE knowledge base. The downside is that it's a BEAST to setup. Once it's setup though it's pretty easy to manage... and did I mention FREE? I like its small footprint. You can install it on a tiny PC running a tiny OS with no graphics and almost zero attack surface area. Plus, even though it's primarily a Linux product, it's Windows-friendly and can use plugins to monitor almost anything Windows related. It has enormous how-to's on monitoring network equipment, routers, switches, etc. Highly customizable; you can create complex notification schedules, targets, dependencies, etc.
Cheers,
TCP handles all of that automatically, there is no need to monitor to detect and panic on no-problems.
I would vote for prtg too.
I would vote for prtg too.
While at it, evaluate NetCrunch network monitor as well. It pretty much does everything you specified above on a very granular level (including automatically generating Layer-2 maps with live usage data).
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Originally, this post was published on Monitis Blog, you can check it
here
.
It goes without saying that technology has transformed society and the very nature of how we live, work, and communicate in ways that would’ve been incomprehensible 5 ye…
- Web Development
- Networking
- Web Development Software
- Monitis
- IT Administration
- *Automation, *DevOps
WARNING:
If you follow the instructions here, you will wipe out your VTP and VLAN configurations. Make sure you have backed up your switch!!!
I recently had some issues with a few low-end Cisco routers (RV325) and I opened a case with Cisco TA…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses
Course of the Month9 days, 7 hours left to enroll
609 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.