Network Monitoring | Voters

181

Network Monitoring

in progress

Akhilesh Subramanian

To automatically detect and monitor devices coming into the network

April 21, 2021

Corey Watson

In my opinion, receiving notifications when devices go offline is sufficient. However, investing in a comprehensive product like Auvik or Domotz just for this purpose seems unnecessary. The only benefit I see in having a discovery feature is to simplify the process of identifying new assets on the network and installing the SuperOps agent on them. That keeps things in the RMM space.

Josiah Bellah

I really appreciate network monitoring coming online. I am currently using Domotz and would like to see an integration there. Multisite scanning with the option to flag important machines and SNMP monitoring.

Erick Grau

I would advise on allowing 3rd party integration "apps" or APIs if anything as a stop gap so they can focus on higher priority items

Ryan Foster

Erick Grau: I agree. I have been trialing Domotz and think that they have a really solid product for the price. If they integrate with them, then it would make SuperOps THAT much more powerful and valuable.

Anirudh K Murthy

marked this post as

in progress

Anirudh K Murthy

marked this post as

planned

Samir Jiwani

Network Monitoring is key and should be focused on.  Even better if it modeled something like PRTG, which we've used for 15 years along side any RMM product we've ever subscribed too.  It's just too good and catches things way before any RMM product does.
Regarding SNMP - Bandwidth counters/error packets etc are all nice to have that info for with respect to switches, and basics for printers to alert client office staff when paper is out, etc, would be cool but not necessary.  I seem to be using less and less of SNMP for alert/monitoring purposes, but we use it only when needed for troubleshooting purposes.
Network Discovery for us is useless.  People always connect mobile phones, smart watches, tablets, etc to their wifi and I really don't care about these devices.  Maybe I should but who has the time.

David Smith

For me they go hand in hand. Discovery to monitor, I'd rather know about potential rogue devices entering the network where possible.

Richard Burt

For me discovery would be better as the first part with the ability to

also

scan / install via workgroups rather than AD etc. SMNP wold be nice too.

You can't monitor without having the discovery first :)

Dallas Turner

I like the idea of working out and fine tuning network monitoring first. Network discovery is nice and all, but as a sysadmin for multiple sites, we have a pretty good pulse on the assets of our clients. Being able to determine when a device is faulty through monitoring before our customers know would be a nice leg up!

Anirudh K Murthy

Hi folks,
We need your help with something. We’re starting to work on the network side of things in the RMM module, and we’re trying to prioritize between network monitoring and network discovery.
Which feature would you like to see on the platform first?
One option that we’re exploring is to provide network monitoring first, where you’ll be able to add assets to the network manually. We’ll then pick up automated network discovery next, and release it down the line.
The alternate plan is to build automated network discovery first, and then build network monitoring features on top of it.
Let me know what you folks think. I’d love your opinion on this. 
(ps. I have a small question to ask. How many SNMP monitored assets do you manage on your client’s networks?)

Angel F Rosa

Anirudh K Murthy: Good day - It would seem that discovery should be the logical path first, then monitoring. After discovering you can allocated and make adjustments to the discovered asset. Continue with monitoring. Cheers - Angel

Erick Baum

Anirudh K Murthy: My vote would be for monitoring first before discovery. I think we probably all use discovery tools already and know what needs to be monitored for existing clients. So being able to add those assets and get up/down alerts would be a good start. Then we could transition to using your discovery later once that's added.

As far as snmp assets, we probably have around 500 devices. If you're talking about individual snmp probes, that would be quite a bit more. Probably closer to 3000 if you consider each switch/router port is a probe that we monitor/graph bandwidth on. We also monitor various snmp metrics on NAS devices, printers, and temperature sensors in server rooms.

Chris Germon

Anirudh K Murthy: I think network monitoring would be preferred to discovery. Discovery without monitoring is pointless I feel.

I have about 400 devices that I managed, about 50 of these I would need SNMP for - printers, routers, switches mainly.

Yoislan Chavez

Angel F Rosa: I would like to see discovery first and then monitoring.

Niklas Riddarlo

Anirudh K Murthy: network monitoring would be preferred our team aswell. You often know what deviced is in the network and right now if customer want us to monitor lets say printer or firewall we cant. Network discovery you can always use a ping sweep or some other free good tools for until Superops can do it.

→