I am fine-tuning the contents of email notifications from the Alarm
Server.

The pre-existing model is this, from the Watchdog:

  From [EMAIL PROTECTED] Mon Jun 16 13:02:02 2008
  From: sipxchange<[EMAIL PROTECTED]>
  Date: Mon, 16 Jun 2008 13:02:00 -0400
  To: [EMAIL PROTECTED]
  Subject: Watchdog Notification

  Message from SIPxchange server: linux-2m7j
  FreeSWITCH:FreeSWITCH Failed MAX restarts. Process can not be
restarted!

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)?  

2: I've set the From string to "Alarm Notification Service"
(localizable).  Any other suggestions?

3: How much info to put into the title?  A short alarm title (no
parameters)?  Just the alarm code (e.g. SPX10002)?  The complete
description, including parameters?  A generic, constant title such as
"Alarm Notification"?  (I am leaning towards a short title, but haven't
implemented it this way yet)

4: Do we still want to send to [EMAIL PROTECTED] by default?

5: Any opinions on how to organize the body?  

6: I have the concept of an alarm code, which is a unique tag meant to
facilitate down-stream processing and documentation (since it is the
same in all languages and is easy to pick out).  I'm thinking of using
SPX plus five digits eg SPX00001, possibly with number ranges assigned
to different components, or possibly just incremented as we add more
alarms.  Any comments on this? 

Thanks for any input,
Carolyn
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to