TANGO
Device Server
Device Server
|
|
|
|
|
|
Device Server |
| |
||
| PhoneBook | Tango::DEVVAR_STRINGARRAY | List of alarms declared like:. User:user@accelerator.es;SMS:+34666555666 |
| |
||
| LogFile | Tango::DEV_STRING | File where alarms are logged |
| PhoneBook | Tango::DEVVAR_STRINGARRAY | List of alarms declared like:. User:user@accelerator.es;SMS:+34666555666 |
| AlarmList | Tango::DEVVAR_STRINGARRAY | List of alarms to be monitorized. The format is:
domain/family/member #It simply checks that dev is alive domain/family/member/attribute > VALUE domain/family/member/State == UNKNOWN domain/family/*/Temperature > VALUE When using wildcards all slash / must be included |
| AlarmReceivers | Tango::DEVVAR_STRINGARRAY | Users that will be notified for each alarm. The format is:
[TYPE]:[ADDRESS]:[attributes];... [TYPE]: MAIL / SMS [ADDRESS] : operator@accelerator.es / +34666555444 [attributes]: domain/family/member/attribute;domain/family/* |
| AlarmDescriptions | Tango::DEVVAR_STRINGARRAY | Description to be included in emails for each alarm. The format is:
TAG:AlarmDescription... |
| AlarmThreshold | Tango::DEV_LONG | Min number of consecutive Events/Pollings that must trigger an Alarm. |
| AlarmEnabled | Tango::DEV_BOOLEAN | If False forces the device to Disabled state and avoids messaging. |
| AlertOnRecovery | Tango::DEV_STRING | It can contain 'email' and/or 'sms' keywords to specify if an automatic message must be sent in case of alarm returning to safe level. |
| FlagFile | Tango::DEV_STRING | File where a 1 or 0 value will be written depending if theres active alarms or not.
This file can be used by other notification systems. |
| PollingPeriod | Tango::DEV_LONG | Periode in ms. in which all attributes not event-driven will be polled. |
| MaxAlarmsPerDay | Tango::DEV_LONG | Max Number of Alarms to be sent each day to the same receiver. |
| MaxMessagesPerAlarm | Tango::DEV_LONG | Max Number of messages to be sent each time that an Alarm is activated/recovered/reset. |
| FromAddress | Tango::DEV_STRING | Address that will appear as Sender in mail and SMS |
| SMSConfig | Tango::DEV_STRING | Arguments for sendSMS command |
| SnapConfig | Tango::DEV_STRING | Arguments for SnapArchiving command |
| AlarmContexts | Tango::DEVVAR_STRINGARRAY | Snap Context to be saved when the alarm is triggered/recovered. The format is:
TAG:ContextName... |
| CreateNewContexts | Tango::DEV_BOOLEAN | It enables PyAlarm to create new contexts for alarms if no matching context exists in the database. |
| Property Name | Default Values</td> |
| PhoneBook | No default value |
| Property Name | Default Values |
| LogFile | /tmp/alarm_$NAME.log |
| PhoneBook | No default value |
| AlarmList | No default value |
| AlarmReceivers | No default value |
| AlarmDescriptions | No default value |
| AlarmThreshold | 2 |
| AlarmEnabled | True |
| AlertOnRecovery | |
| FlagFile | /tmp/alarm_ds.nagios |
| PollingPeriod | 60000 |
| MaxAlarmsPerDay | 3 |
| MaxMessagesPerAlarm | 3 |
| FromAddress | controls |
| SMSConfig | : |
| SnapConfig | : |
| AlarmContexts | No default value |
| CreateNewContexts | True |
TANGO is an open source project hosted by :
|
Core and Tools :
CVS repository on
tango-cs project
Device Servers : CVS repository on tango-ds project |