Being new to Orbit (coming from the Server Command side), I have found a lot of new and very interesting features it contains. I really like what I have seen. Looks like a pretty decent package. I am now looking into the Escalation Procedures listed under Orbit Setup. It appears to be where I can set a procedures that I want Tech Support to take in the event taht the server has issues and I am not around to provide guidance. Right now all that I have as options in the combo box is 1) General Escalation and 2) my name (ip). This is on a cPanel/RHEL box. Can someone give me a little advice as to what all might be a good suggested starting point for building my Escalation Procedures?

Thanks,
DB

Escalation procedures can be anything from, create a ticket and do nothing, to reboot the server, to call me at these numbers 1.xxx 2.xxx 3.xxx.

Escalation procedures are separated by hardware object, or 'general escalation procedures'. The #2 option you see above is how orbit has your server 'labeled' you can open a ticket to have this changed to a more 'user friendly' label if you would like. Most of our customers have 'general escalation procedures', then if they have any exceptions to the rule (like a database server or something), they will create a specific escalation procedure for that server.

Here is an example of how I would setup my escalation procedures for a production web cluster with a single backend database server.



This would allow any of the nodes running the web service to just be restarted unless there is a problem, and to call me for action on the database server.

One thing to point out though, you should have a course of action for 'every' service/process/status that you are having us monitor, as we will be alerted to those as well.