Skip to content

Standardise log levels #223

@AlfioEmanueleFresta

Description

@AlfioEmanueleFresta

Analyse the codebase for use of logging, write a policy.

Starting point:

  • warn! for unexpected device behaviour
  • error! for library errors only
  • trace! for verbose bytearray dumps, debug! only lenghts or very small, relevant fields
  • Sensitive request/response content at debug! or more verbose only
  • debug!({ %foo, ?bar }, "Static comment") and error!(?err, "Error message") over string interpolation

Bonus point for automated linting checks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions