Quote:
Originally Posted by
deepm
Ok as you said some systems have to be monitored hourly, so i want to know what are the things to be monitored hourly is it just restricted to FileSystem, Memory.....?
Ask yourself what it is that keeps a system going (that is: fulfilling its purpose). This is your answer.
If anything has to be monitored every minute, hour, day, week or month depends on the system and the characteristics of its purpose. There is no general answer because there is no "general system".
If you ask "which is the best car" without specifying for which purpose the only thing one could answer is: that depends. If you want to transport tons of goods it might be some large truck and not the Ferrari, if you want to win races it might be the other way round and if you want to go offroad you will quickly find out that both are quite bad compared to a Landrover.
Coming back to your question: what does a system keep going:
a) environmental issues
- energy
- climate/temperature control
- ....
b) OS level
- availability of processing resources - CPU
- availability of memory
- availability of storage space - filesystem
- OS resources consumption: process table, etc.
- availability of network bandwith
- ...
c) application specific
- depends on the application, things like queue lengths, transaction times, ...
Be aware that this list is far from being complete, its just the most obvious things, feel free to add whatever is important for
your system to continue working. As a rule: everything that
is important for the system to continue doing its purpose you need a "sensor" - a logfile, a piece of software, a blinking warning lamp, what ever.
Some of the things might be already covered: you do not have to watch climate control if the system is in a data center where air condition is provided and covered for without you doing anthing. You still might want to watch over fans, etc. and get an alarm if the system starts overheating.
Speaking about the things left on the list: it depends on the system and what it is used for, how often something has to be checked. Because these checks take usually some processing power (in most cases little programs do the work) it is generally good to do the checks as often as necessary and as rarely as possible. If you have a system where never data gets stored (a gateway system, for instance) a check of the filesystems every minute is superfluous, on a database server it might be necessary. The same goes for CPU, network and all the other things on the list.
So there is no such thing as a "thing that has to be monitored hourly", because, whatever the thing in question is, depending on the specifics of the system one hour might be an overkill as well as far too little.
I hope this helps.
bakunin