#157 - Configure the level of the end of process logs

[njoubert-cleverage]

Description

Fixes #157, as proposed in this comment: without UI, the Process <code> succeed log is the only way to follow processes, so it stays info by default, but its level can now be configured, and a Process <code> failed log is added.

clever_age_process:
    logs:                          # global defaults
        success_level: info        # default
        failed_level: debug        # default
    configurations:
        app.hourly_import:
            logs:                  # override for this process only
                success_level: debug

• success_level is used for Process <code> succeed (it was always info).
• failed_level is used for the new Process <code> failed log, written when a process fails:
  • with an exception (in addition to the existing Critical process failure log);
  • or when it is stopped without exception, e.g. by a StopTask (such a run had no end of process log at all).
• Both logs have the duration of the process in their context. Levels are validated by the configuration (RFC 5424 severities, as the task log_level).
• ProcessConfiguration exposes getSuccessLogLevel() / getFailedLogLevel(), and ProcessConfigurationRegistry gets an optional third argument with the default levels.

Checked end-to-end in process-bundle-demo (demo.logs.success_level logs its success as NOTICE, demo.logs.stopped logs Process demo.logs.stopped failed as WARNING, other processes are unchanged).

Requirements

• Documentation updates
  • Reference
  • Cookbooks
  • Changelog
• Unit tests

Breaking changes

None: default levels keep the current behavior, the new failed log is debug by default. New constructor arguments are optional.

🤖 Generated with Claude Code