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

Logging #45

Open
tony opened this issue Mar 13, 2022 · 0 comments
Open

Logging #45

tony opened this issue Mar 13, 2022 · 0 comments

Comments

@tony
Copy link
Contributor

tony commented Mar 13, 2022

To aid, I would propose we add logging to the package

  1. job name, args, kwargs + generating ID
  2. checking for lock
  3. creating lock
  4. clearing lock

By default, they'd be at a super-low logging level, e.g. DEBUG (or NOTSET?)

Additionally / optionally:

  • pure python example of setting the logging levels, to stdout, etc.

    (this treads a bit into helping the user do what they could themselves as it's standard library, but I think that logging is actually configured/tweaked rarely enough its helpful to the user to see an example)

  • setting a global baseline, e.g. CELERY_SINGLETON_LOG_LEVEL, comparable to DJANGO_LOG_LEVEL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant