Skip to content

Logging #4

@pointan

Description

@pointan

Currently, the ML policy is that we don't log anything. The reason being that Log4J is unreasonably slow. The problem isn't the logging itself, but the Check at which loglevel we are is incredibly slow. Currently, we don't have logging AT ALL, which is problematic.

In this issue:

  • Purge the last remnants of log4j from ML
  • Implement a logger. (Note that Analytics is NOT intended as logging framework!)
  • Supplement the existing algorithms with logs → Most important is ERROR, but Debug and Info are nice to have as well.

Metadata

Metadata

Assignees

No one assigned

    Labels

    confirmedRequest was accepted and will be worked on

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions