Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • lutra lutra
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 155
    • Issues 155
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OTTROTTR
  • lutralutra
  • lutralutra
  • Issues
  • #396
Closed
Open
Issue created Nov 30, 2022 by ostahluio@ostahluioMaintainer

Lutra should become more logger-friendly

Currently lutra mostly writes results and messages directly into streams and this is often done quite deep down in the system.

While not a problem for CLI-usage, this makes things difficult when using logging (e.g. on a server) and/or when console-output is not easily available. The mix-up between program output and technical output complicates things even more.

Lutra should separate program/user-centered output from technical output and become more logging-friendly.

A flexible approach could be to channel all output into one or more loggers and let logging configurations decide where to print what. This would keep the current convenience level for the CLI while enabling server-users to re-configure logging for their needs.

Assignee
Assign to
Time tracking