Share what you know with millions of people

Focus is the best place to turn what you know into remarkable content
×
0

What should I keep in mind when deploying monitoring software?

What is the most important aspect of a monitoring software deployment project? What do I need to do to ensure a successful project?

Attachments

0
Benjamin Breeland
Enterprise Management Consultant, ca technologies
Posted on Nov. 30, 2010
  • Recommended by:

My suggestion is to focus on one critical application or service and monitor everything about it to establish baselines. If possible, avoid the "discover everything" approach and focus on a single application or critical service (email is a good one). This method provides visibility into the network and the supporting infrastructure while allowing you to become familiar with the monitoring software and how to use it to accomplish your goals. If you have specific goals (reports, SLAs, performance goals), then create models of these first, so that your deployment supports the information you wish to receive.

If possible, use this as your method to evaluate monitoring software vendors. If the vendor can successfully monitor one critical application or service during an evaluation, then the vendor has a good chance of handling the rest of your monitoring challenges.

Good luck!

If possible, use this as your method to evaluate monitoring software vendors. If the vendor can successfully monitor one critical application or service during an evaluation, then the vendor has a good chance of handling the rest of your monitoring challenges.

Good luck!

0
Erik Goldoff
IT Systems & Security consultant, Goldoff Consulting
Posted on Nov. 30, 2010
  • Recommended by:

The most important part of your monitoring software deployment project is understanding what assets you have so that you can include the proper monitoring metrics, and then creating your baselines.

What are you intending to monitor ? Servers, Routers, web traffic, malware detections, etc ? For each category to be monitored, make sure you can display and trigger on those metrics that will prove important to you.
Servers : CPU utilization, Disk Space, Memory, Concurrent Connections, NIC utilization, page faults, database size, etc
Routers : CPU Utilization, interface bandwidth, Memory, dropped packets, interface up/down, etc
Web Site : Visitor count, browser distribution, referral page, errors by category (404, 500, etc ), in addition to regular server metrics

I often preach that it is very important to properly record your baselines, so that you can properly set your alert triggers.
This leads to a secondary focus for the deployment, your alerting capability. Beyond the recording and display of results, can you trigger real time alerts to SMS text, SMTP email, warning lights, and do you have multiple methods of communicating these alerts. For example, if your internet circuit is down, do you have a POTS ( Plain Old Telephone Service ) line and modem as an alternate for text and email ?

Answer This Question