Skip to content
This repository has been archived by the owner on Sep 14, 2020. It is now read-only.

Improving logging when loading modules #348

Open
2 tasks done
mnaser opened this issue Apr 17, 2020 · 0 comments
Open
2 tasks done

Improving logging when loading modules #348

mnaser opened this issue Apr 17, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@mnaser
Copy link

mnaser commented Apr 17, 2020

First of all, excellent work on the operator, we're moving away from kubebuilder and adopting it here:

https://opendev.org/vexxhost/openstack-operator

Slowly but surely, the codebase is shaping up. :)

Problem

It's simple, the logs when loading it via a module don't give you enough information about the module which the function is called from, for example, we frequently call the 'create' function as create and so looking over the logs, we can't tell which operator was the one that did the create.

Proposal

It would be nice if we had a prefixed path, something like:

openstack_operator.memcached.create

Or something along those lines.

Checklist

  • Many users can benefit from this feature, it is not a one-time case
  • The proposal is related to the K8s operator framework, not to the K8s client libraries
@mnaser mnaser added the enhancement New feature or request label Apr 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant