Event Structure
Events from Amlyze are delivered using Binary Content Mode. This means that identifications about object and event type are passed via HTTP header. Those headers, based on specification, have ace- prefix.
Passing information in such way, allows identifying information prior parsing the body, thus allowing more dynamic handling for the incoming events.
Header Mapping
| Cloud Event HTTP Header | Correlation With Amlyze |
|---|---|
| ce-id | Unique event ID. Unique per event. |
| ce-source | Event Source. RFC 3986 - Uniform Resource Identifier (URI). In most cases returns value from communicationNumber. |
| ce-specversion | Cloud Events Specification version. Currently - 1.0. |
| ce-subject | Event subject, represents a resource’s (customer, related entity, operation) external id. |
| ce-time | Event time. |
| ce-type | Unique event type. |