You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Serge Huber (Jira)" <ji...@apache.org> on 2025/02/27 16:02:00 UTC

[jira] [Assigned] (UNOMI-873) "Explain" for event collection

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

Serge Huber reassigned UNOMI-873:
---------------------------------

    Assignee: Serge Huber

> "Explain" for event collection
> ------------------------------
>
>                 Key: UNOMI-873
>                 URL: https://issues.apache.org/jira/browse/UNOMI-873
>             Project: Apache Unomi
>          Issue Type: Sub-task
>            Reporter: Romain Gauthier
>            Assignee: Serge Huber
>            Priority: Major
>
> h3. Context: 
> When sending an event to unomi, it can be hard to understand: 
> - why the event was rejected 
> - which rules where executed 
> - what was the final request sent to ES 
> All these information can be useful during development, when trying to understand why and how an event is processed.
> h3. Idea
> We could either:
> -  create a dedicated http endpoint "explainEvent" that would return the explanations as part of the http response
> - add an option ?"explain=true" to context.json endpoint. We'd need to ensure that this option is protected by authentication. 



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