Following discussions on slack it was agreed that the way we model events that are part of some hierarchy, e.g. one event is the child of another, or events that form part of a session needs improving.
The proposed solution is
<EventSource>
<EventId>abcdefg</EventId> <!-- A unique id known to the source system that created the event -->
<SessionId>JSESSION12345</SessionId> <!-- A session id if the event was created as part of a session (can be used to associate events by session) -->
</EventSource>
<EventDetail>
<!-- leave alone -->
</EventDetail>
<EventParent> <!-- Can we change EventChain to EventParent - might be more obvious unless we think we are describing sibling rather than parent child relationships? -->
<EventId>12344</EventId> <!-- the Id (EventSource/EventId) from the parent event -->
<EventParent>
<EventId>12343</EventId> <!-- the Id (EventSource/EventId)from the parent of the parent event -->
</EventParent>
</EventParent>
</Event>
Following discussions on slack it was agreed that the way we model events that are part of some hierarchy, e.g. one event is the child of another, or events that form part of a session needs improving.
The proposed solution is
EventParent
would replaceEventChain