BatchResponseEvent Object | Field | Type | Description | Kafka Header | Event Payload Field | Notes | CloudEvents Mapping |
|---|
| eventID | string | The unique id identifying the event generated by DMI | x |
| Mandatory | Generated by DMI-Plugin | | eventCorrelationId | string | The request id passed by NCMP | x |
| Mandatory. This is requestId that NCMP sent to client as an ACK.
Example : “request-1234" (UUID) | extensions (correlationid) | | eventTarget | string | The destination topic of the client | x |
| Mandatory. TBC example: my-topic | extensions ( target TBC) | | source | string | The source of the event |
|
| Optional. Example : dmi-plugin:enm-1 (dmi service name) |
| | eventTime | string | The timestamp when original event occurred | x |
| Optional. The timestamp should follow that on https://www.rfc-editor.org/rfc/rfc3339#section-5. This follows ISO 8601 and is what is used/referenced in 3GPP standards
Example: 1985-04-12T23:20:50.52Z this represents 20 minutes and 50.52 seconds after the 23rd hour of April 12th, 1985 in UTC. | standard ( time) | | eventType | string | The type of the event | x |
| Mandatory. NCMP owns eventType that would be used by dmi-plugins
The Convention of eventType and Schema names is under discussion, see open issue |
| 