22 is_closed_loop_disabled:
31 - is_closed_loop_disabled
34 description: Common fields for control loop events and notifications
36 closedLoopControlName:
38 description: A UNIQUE string identifying the Closed Loop ID this event is for. There are no semantics behind this string.
40 $ref: '../../../../sdc/src/main/resources/definitions.yaml#/serviceInstance'
42 $ref: '../../../../sdc/src/main/resources/definitions.yaml#/resourceInstance'
45 description: This is required via ONAP Platform Logging Requirements.
46 pattern: /[a-f0-9]{8}-[a-f0-9]{4}-4[a-f0-9]{3}-[89aAbB][a-f0-9]{3}-[a-f0-9]{12}/
49 description: ID that maps back to Highland Park. Concatenation between eventID and firstEPOCH.
52 description: pulled from eventSourceName of trigger H.P. alarm. The contents of this field should also be contained in the AAI Json sub-tag (see below).
55 description: firstEpoch. UTC Timestamp when this event was detected by DCAE. Conform to ONAP Logging requirements.
58 description: lastEpoch. UTC Timestamp when this event was detected as cleared by DCAE. Conform to ONAP Logging requirements.
59 closedLoopEventClient:
61 description: Open DCAE sub-system that detected the event and published this event message.
64 description: The target entity that is being administered. This could be VM_NAME, VNF_NAME, etc. This should map to a field name in the AAI sub-tag shown below.
76 - closedLoopControlName
80 - closedLoopAlarmStart
81 - closedLoopEventClient
90 - $ref: '#/ControlLoop'
92 closedLoopEventStatus:
94 description: The status for the event within Open DCAE. A value of “ONSET” indicates the event has been encountered. “ABATED” indicates the event has been abated.
99 - closedLoopEventStatus
101 - $ref: '#/ControlLoop'