On Jun 17, 2008, at 4:35 PM, Liane Praza wrote: > Totally agreed. We've called this "Transitions", and while I put > some of the plumbing into svc.startd to make it easier a while ago, > we haven't managed to actually staff this work yet. Transitions > would allow you to select between an SNMP trap, email notification, > or simple execution of a shell script on a specified state transition.
Excellent. Might there be a design doc floating around that could be posted to the files area of the SMF community? > (The only real tricky part is the configuration of messages. Some > sites may not want notification of all transitions for all > services. An easy an flexible way to describe the desired policy is > important. The rest is a fairly straightforward fault-tolerant > coding exercise.) I imagine this would be set in the service's manifest. Each "transition method" (I'm just coming up with a name here) such as SNMP traps, email, program exec, etc could be defined in the service's manifest, with each method having an on/off flag under for each of the possible states of groupings of them (online/offline/degraded/ maintenance etc.) So for example one might want the SNMP trap transition method for all services set to on when the state is starting or degraded, but have SNMP traps and emails enabled for certain other services for only when the enter or exit degraded and maintenance mode. Is this close to what you are envisioning? /dale
