You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@unomi.apache.org by "Jonathan Sinovassin-Naïk (Jira)" <ji...@apache.org> on 2022/08/25 07:41:00 UTC

[jira] [Assigned] (UNOMI-623) Store original event id and event type inside session

     [ https://issues.apache.org/jira/browse/UNOMI-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Sinovassin-Naïk reassigned UNOMI-623:
----------------------------------------------

    Assignee: Jonathan Sinovassin-Naïk

> Store original event id and event type inside session
> -----------------------------------------------------
>
>                 Key: UNOMI-623
>                 URL: https://issues.apache.org/jira/browse/UNOMI-623
>             Project: Apache Unomi
>          Issue Type: Improvement
>            Reporter: romain.gauthier
>            Assignee: Jonathan Sinovassin-Naïk
>            Priority: Major
>
> Unomi has some behaviours that are hard to guess regarding session creation. 
> To be able to identify why and when new sessions are created, it would be great to add the id of the event that triggered the session creation and its event type. 
> I suggest that we create new fields orginEventId and originEventType in the session, maybe in the source?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)