Setting Common Attributes Sample Clauses

Setting Common Attributes. ‌ The tables presented in Section 6.2 refer to attributes defined in [2]. The following list provides recommendations regarding how to populate these attributes. 30 • Correlation ids - They are supplied to correlate two notifications that have been generated because of a related cause. This attribute is optional; however, in case of alarms that are generated to clear certain conditions, that is, produced with a perceived severity of SA_NTF_SEVERITY_CLEARED, the correlation id 35 shall be populated by the application with the notification id that was generated by the Notification Service when invoking the saNtfNotificationSend() API during the production of the actual alarm. • Event time - The application might pass a timestamp or optionally pass an SA_TIME_UNKNOWN value in which case the timestamp is provided by the 40 Notification Service. • NCI id - The notification class identifier is an attribute of type SaNtfClassIdT. The 1 vendorId portion of the SaNtfClassIdT data structure must be set to SA_NTF_VENDOR_ID_SAF always. The majorId and minorId will vary based on the specific SA Forum service and the particular notification. Every SA Forum service shall have a majorId as described in the enumeration SaServicesT (see 5 [1]). • Notification id - This attribute is obtained from the Notification Service when a notification is generated, and hence need not be populated by an application. • Notifying object - DN of the entity generating the notification. This name must 10 conform to the SA Forum AIS naming convention and contain at least the safApp RDN value portion of the DN set to the specified standard RDN value of the SA Forum AIS service generating the notification, which in this case is “safApp=safLogService". For details on the SA Forum AIS naming convention, refer to the SA Forum Overview document ([1]). 15