You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Kevan Jahanshahi (Jira)" <ji...@apache.org> on 2022/07/20 14:14:00 UTC

[jira] [Created] (UNOMI-630) Implement a global solution to avoid multiple same log pollution.

Kevan Jahanshahi created UNOMI-630:
--------------------------------------

             Summary: Implement a global solution to avoid multiple same log pollution.
                 Key: UNOMI-630
                 URL: https://issues.apache.org/jira/browse/UNOMI-630
             Project: Apache Unomi
          Issue Type: Task
            Reporter: Kevan Jahanshahi


It happen multiple time already where we tried to deprecate stuff and log messages (warn, error, info) like:
 * no action in rule
 * empty condition
 * "now" property deprecated on condition
 * etc ...

And the problem with that is that this logs can really be logged a millions time depending on the events receved and rules triggered, always triggering them.

The best approach would be:

Study a system to avoid logging the same log x Times on a time period. Because those logs are still interesting for the users/integrators as they can enlighten bad implem or stuff to be migrate/update. 

See if we can do something at log4j level.

The main goal are:
 * light the logs to avoid huge log file that contains millions time same lines
 * keep the useful information



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