Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add logs add targets with more details #86

Open
kairoaraujo opened this issue Sep 1, 2022 · 4 comments
Open

Add logs add targets with more details #86

kairoaraujo opened this issue Sep 1, 2022 · 4 comments
Assignees
Labels
good first issue Good for newcomers hacktoberfest Opt-in with this issue to Hacktoberfest and indicate you’re looking for contributions.

Comments

@kairoaraujo
Copy link
Member

Add more logs for add targets.

@kairoaraujo
Copy link
Member Author

Extend it to kaprien-repo-worker

@kairoaraujo kairoaraujo modified the milestones: v0.0.1a1, v0.0.1b1 Sep 26, 2022
@kairoaraujo kairoaraujo reopened this Oct 25, 2022
@kairoaraujo
Copy link
Member Author

It was closed by mistake. Issue reopened.

@MVrachev
Copy link
Member

What about we discuss a prefix of our logs which will help us identify where this log comes from?

@lukpueh
Copy link
Collaborator

lukpueh commented Oct 2, 2023

See Logging HOWTO

A good convention to use when naming loggers is to use a module-level logger, in each module which uses logging, named as follows:

logger = logging.getLogger(__name__)

This means that logger names track the package/module hierarchy, and it’s intuitively obvious where events are logged just from the logger name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers hacktoberfest Opt-in with this issue to Hacktoberfest and indicate you’re looking for contributions.
Development

No branches or pull requests

4 participants