On Mon, 2008-06-16 at 14:51 -0400, Carolyn Beeton wrote: > This is how it looks now in my current implementation: > > From [EMAIL PROTECTED] Mon Jun 16 13:01:57 2008 > From: "Alarm Notification Service" > <[EMAIL PROTECTED]> > To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > Cc: > Subject: Process FreeSWITCH was found in a non-running state, and > failed MAX restarts. Process cannot be restarted! > Date: Mon, 16 Jun 2008 17:01:57 GMT > Mime-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > > Alarm W10002 reported at 2008-06-16T17:01:50.229116Z on > linux-2m7j.example.com: > Process FreeSWITCH was found in a non-running state, and failed MAX > restarts. Process cannot be restarted! > If the process is required, check logs for more details and contact > support. > > Questions. > > 1: I've seen mentioned that we want to avoid hard-coding the product > name. Should I put the product into the AlarmDefinitions.xml, where > it could even be customized? Should the default be sipXecs? or is > the product name available some other way? or does the product need to > be there at all (it isn't in my current implementation)?
I don't know how you'd want to configure the product name, but it seems to me that a Subject like "sipXecs alarm notification" would be good. The product name reminds the reader what the message is about, and helps the message stand out from all the spam. (I've learned to never title messages to people I haven't talked to recently with "Hi there!" and similar things.) Using the same Subject for all notifications seems smart, as that makes it easy to filter for. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
