Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
 Post subject: Check Failure Escalation
PostPosted: Sat Feb 02, 2013 12:16 pm 
Offline
Newbie

Joined: Sat Feb 02, 2013 12:07 pm
Posts: 2
Website: http://mike.crute.org
Location: Cleveland, Ohio
Would it be possible to allow a check failure to first notify one of the contact groups in my organization before it notifies the Linode team? The way I'm thinking of using the managed service as a fallback for my ops team. If a check fails, notify my ops team and if nobody responds in a reasonable time (say 5 minutes but perhaps this could be configurable based on our internal SLA for the service) then the Linode team takes over and makes the fix instead.

I don't really have a dedicated ops team but a few of my developers have the ability to access the boxes and can make changes to the puppet configs. I would prefer that as a first line of defense and Linode as the fallback.

Is that reasonable or am I missing the point?


Top
   
PostPosted: Wed Feb 06, 2013 12:43 pm 
Offline
Linode Staff

Joined: Thu Jan 10, 2013 9:43 am
Posts: 11
Linode Managed was designed to notify Linode staff first and foremost, and it is our responsibility to notify your contacts as part of our response to the issue. You could certainly just request that we notify your team of the issue instead of us responding by fixing, but there isn't a system in place for us to start normal procedures after a period of time has passed without response.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group