-
Notifications
You must be signed in to change notification settings - Fork 26
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
switch to structured logging #126
base: main
Are you sure you want to change the base?
switch to structured logging #126
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pinikomarov The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @pinikomarov. Thanks for your PR. I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
ffeec05
to
3663643
Compare
97d401a
to
7582147
Compare
/ok-to-test |
/retest-required |
7582147
to
49e37b9
Compare
recheck |
update logging fix name update test logging update logging update logging Structured logging
49e37b9
to
fc55570
Compare
recheck |
1 similar comment
recheck |
/test manila-operator-build-deploy-tempest |
@pinikomarov It looks like something isn't happy with the code:
|
/retest |
hi @abays , that's weird , do you know why the test complains about lines that are different in the patch?
But those locations (on manila_controller.go) are not as they they are in the patch: |
/retest |
1 similar comment
/retest |
@pinikomarov: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@pinikomarov can you rebase? |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
This automatically adds additional fields like reconcile_id etc.. from the controller context.
before :
2023-05-18T01:53:14+03:00 INFO controllers.KeystoneAPI Reconciled Service init successfully
after:
`2023-10-19T12:26:41+03:00 INFO Controllers.ManilaAPI Reconciling Service 'manilaapi-sample' {"controller": "manilaapi", "controllerGroup": "manila.openstack.org", "controllerKind": "ManilaAPI", "ManilaAPI": {"name":"manilaapi-sample","namespace":"openstack"}, "namespace": "openstack", "name": "manilaapi-sample", "reconcileID": "360c1316-82f3-4b34-a510-8030ca39fefb"}
`
*by using per reconcile function respective logger objects, the intention is to lay the ground for parallel reconciliation in future and avoid race conditions as ctx objects are reconcile run specific.