[
https://issues.apache.org/jira/browse/UNOMI-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-533:
------------------------------
Description:
We currently have a system for [rule
statistics|https://github.com/apache/unomi/blob/master/api/src/main/java/org/apache/unomi/api/rules/RuleStatistics.java]
that accumulated times for rule conditions and actions, but we could try to
make it finer-grained to:
- count execution time by condition and action type
- accumulate errors for rule executions, avoiding polluting logs for errors
that repeat a lot
Open questions remain for the error reporting part, as to how they are
collected and if they can be associated with condition/action types or not.
It could also be interesting to get "generic" or "last" logs and execution
times for a rule execution, to help with rule debugging/tracing
was:
We currently have a system for [rule
statistics|https://github.com/apache/unomi/blob/master/api/src/main/java/org/apache/unomi/api/rules/RuleStatistics.java]
that accumulated times for rule conditions and actions, but we could try to
make it finer-grained to:
- count execution time by condition and action type
- accumulate errors for rule executions, avoiding polluting logs for errors
that repeat a lot
Open questions remain for the error reporting part, as to how they are
collected and if they can be associated with condition/action types or not.
> Add finer grained rule statistics and error reporting
> -----------------------------------------------------
>
> Key: UNOMI-533
> URL: https://issues.apache.org/jira/browse/UNOMI-533
> Project: Apache Unomi
> Issue Type: Improvement
> Components: core
> Reporter: Serge Huber
> Priority: Major
> Fix For: 2.0.0
>
>
> We currently have a system for [rule
> statistics|https://github.com/apache/unomi/blob/master/api/src/main/java/org/apache/unomi/api/rules/RuleStatistics.java]
> that accumulated times for rule conditions and actions, but we could try to
> make it finer-grained to:
> - count execution time by condition and action type
> - accumulate errors for rule executions, avoiding polluting logs for errors
> that repeat a lot
> Open questions remain for the error reporting part, as to how they are
> collected and if they can be associated with condition/action types or not.
> It could also be interesting to get "generic" or "last" logs and execution
> times for a rule execution, to help with rule debugging/tracing
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
