Hi Rick!
What was your issue? Is it likely to repeat itself? Was the issue reported in the Alerts log?
You can monitor the individual processes, using a tool like Open View, or implement SNMP to script that will allow you to process control-M alerts.
You need to define what are your risks, and then what your likely root causes are, and then apply your monitors.
As for "best practice", standard services and processes monitoring is always good to do, if you know them, or you can monitor for indirect effects, like a job not running.
Lastly, Control-M has daily maintenance jobs to run, like the db check, or the stat collection. Some of those will generate alert log messages that you can trap.
Give us some more meat, and you will get better customized answers!
Happy Holidays!
Daniel Companeetz.
--- On Tue, 12/23/08, greenlilytree <greenlilytree@...> wrote: From: greenlilytree <greenlilytree@...> |
Yahoo! Groups TipsDid you know...Hear how Yahoo! Groups has changed the lives of others. Take me there. |
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
|
||||||||||||||||||||||||||||||
Offline 
Send Email