Hi Jon, Its long time ago for me, but I'm rather sure sysedge can do that by its own.
You can watch processes with sysedge and start an action if process is down. Write in sysedge.cf something like that and restart agent #watch process procAlive 'regexp' index flags interval 'descr' 'action' With best regards, Frank Wagner Siemens AG Siemens IT Solutions and Services Global Operations SIS GO OM PT3 Siemensstr. 2-4 90766 Fuerth, Germany Tel.: +49 (911) 978-2094 Fax: +49 (911) 978-2037 Mobile: +49 (173) 9756106 mailto:[email protected] Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; Managing Board: Peter Loescher, Chairman, President and Chief Executive Officer; Wolfgang Dehen, Heinrich Hiesinger, Joe Kaeser, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y. Solmssen; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322 -----Ursprüngliche Nachricht----- Von: Jon Whitehouse [mailto:[email protected]] Gesendet: Dienstag, 19. Mai 2009 17:52 An: spectrum Betreff: RE: [spectrum] Process Monitoring Let me be a little more specific I have a Sun server with a SystemEDGE agent on the box. The application team has a process that keeps dying at odd times during the night. They have asked if I can monitor for the process and if it drops, restart it. Solution 1: Would be to just write a script on the server itself, check for the process and if down restart and run it through cron. If it doesn't come up send a trap to spectrum to generate an alarm. The problem with this solution is that I have to write the script on the server and remember that I put it there. Also, the cron would always run the script regardless of if the process was up or down. Solution 2: Monitor the process with spectrum, figure out way to restart process if down and if doesn't start send alarm. This solution is better because I have 1 centralized place to monitor and keep all my scripts at. When you have 700+ servers this becomes ideal. Now I don't have to remember that I have "custom scripts" on each server. Everything is in one place. - If I were to use the SystemEDGE agent, it is no better than writing the script on the box... it's another configuration that I would have to keep track of server specific. - I do have Spectrum Configuration Manager but I believe I can only do stuff with network devices and not servers. (at least all I see in the Device families are network devices) - I'm not sure I want to muck with the SetScript to write another script to connect to a server and execute a command. Seems like a bit overhead to me. So it seems my only option would be to use eHealth for this task from what I'm seeing. --- Jon Whitehouse Systems Engineer - IT, Server Support MS 5221 1800 W. Center Street Warsaw, IN 46580 (574) 371-8684 (574) 377-2829 (cell) [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
