Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

Unify and enchance conrtainer tracer logging #4

Open
tzstoyanov opened this issue Jan 25, 2023 · 0 comments
Open

Unify and enchance conrtainer tracer logging #4

tzstoyanov opened this issue Jan 25, 2023 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@tzstoyanov
Copy link
Contributor

tzstoyanov commented Jan 25, 2023

Currently a mix of prints and logs are used to dump important runtime information

  • Use go log module for logging, replace all prints with logs.
  • Add verbosity levels and categories of the logs.
  • Implement logic for setting the verbosity and category of the logs, at startup and runtime.
  • Sort the existing logs to appropriate verbosity and category and use the relevant log function.
  • Add more informational, debug and warning logs.
@tzstoyanov tzstoyanov added enhancement New feature or request good first issue Good for newcomers labels Jan 25, 2023
@tzstoyanov tzstoyanov changed the title Unify and enchance conrtainer tracer logging. Unify and enchance conrtainer tracer logging Jan 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant