...
Field | Type | Description | Mandatory? | Notes |
|---|---|---|---|---|
id | string | The unique id identifying the event | Mandatory | Generated by DMI-Plugin |
correlationid | string | The request id passed by NCMP | Mandatory | It's requestId that NCMP sent to client as an ACK. Example : “request-1234" (UUID) |
time | string | The timestamp when original event occurred | Optional | The timestamp should follow that on https://www.rfc-editor.org/rfc/rfc3339#section-5. This represents 20 minutes and 50.52 seconds after the 23rd hour of April 12th, 1985 in UTC. |
target (TBC) | string | The destination topic of the client | Mandatory | Example : my-topic |
source | string | The source of the event | Optional | Example : dmi-plugin:enm-1 (dmi service name) |
type | string | The type of the event | Mandatory | NCMP owns eventType that would be used by dmi-plugins convention of eventType and Schema names is under discussion, see open issue #17 |
datacontenttype | string | The schema and version of the Batch event payload. | Mandatory | NCMP owns eventSchema that would be used by dmi-plugins |
Now included in datacontenttype | ||||
| specversion (default 1.0) | String |
...