Discussion Locked

Recommendations for Systems/Network Management

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have been tasked with coming up with an integrated solution for monitoring our backoffice systems and network. It's mostly Windows, on the server side but also some Linux and Solaris. HP networking gear. About 600 nodes all together.

We have a real jumble of monitoring tools currently which makes it very hard to manage and get an overall picture of what is going on.

I had a very frustrating experience talking to HP about OpenView - it looks like they could do most of what we are looking for, but at a serious price by the time you add up all the modules and implementation costs.

Really interested in pulling together performance data from WMI/SNMP/other as well as log/trap data and be able to report and alert off it all seamlessly.

What other tools should I be looking at? I don't think our budget will stretch to a full framework solution - but that may be a good thing!

6 replies

by j.bransom

Integration is the trick - there are a ton of products out there, but making them work nicely together is half the battle.
My last company bought ScienceLogic EM7 and they sound pretty happy with it - the Exchange reporting is very sharp from what I've seen. It was just reviewed in Network Computing if you want to take a look.

by srubik

Thanks - I had not heard of this before. I just went through a web demo - VERY slick!

The ticketing piece is definately a bonus.
Negotiating to get a demo unit, so we'll see how that goes.

by a.evans

Many organiations do not have mature processes in place to help determine what tools to select so often they are selected on funtionality and ease of use. whilst this is useful, until you have determined what your processes need from a toolset you wont know what requirements you have for the toolset. for example; what does the capacity management process need from the tool or what does the Incident Management Process need from the tool, or what are the requirements of the tool from a configuration management perspective or from a Service Level Management perspective, so on and so forth. If you buy a tool and customise it to the way you work this becomes a big maintenance headache. I would recommend aligning internal processes to a standard framework like ITIL and then you will have a clear view of the toolset requirements. This will reduce customisation of internal processes to fit the tool as most tools thesedays will claim to support the standard ITIL framework.

Hoope this helps

by granville

I have been "playing" with Spiceworks for...well some months now.

I find it does very nearly everything I need, and most of the rest I can get from built-in monitors.

Mind you I have a fairly small site with just 5 servers, 70+ nodes and 10 or so "network devices".

At the price I would back j.wilson11's suggestion that you give it a trial. The more people using it, the more features Spiceworks will be able to include.

This discussion is closed to new replies.