redhat-cop / redhat-cop/group-sync-operator
log messages in mixed format
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
When we display the log of the group-sync-operator the time format is mixed.
Can we change the date/time format for all messages to a more readable version?
xMMDD HH:MI:SS.ssssss
1.6921816787539868e+09 INFO controller-runtime.metrics Metrics server is starting to listen {"addr": "127.0.0.1:8080"}
1.6921816787543995e+09 INFO setup starting manager
1.6921816787546647e+09 INFO Starting server {"path": "/metrics", "kind": "metrics", "addr": "127.0.0.1:8080"}
1.6921816787547314e+09 INFO Starting server {"kind": "health probe", "addr": "[::]:8081"}
I0816 10:27:58.754788 1 leaderelection.go:248] attempting to acquire leader lease group-sync-operator/085c249a.redhat.io...
I0816 10:28:53.566548 1 leaderelection.go:258] successfully acquired lease group-sync-operator/085c249a.redhat.io
1.6921817335676498e+09 INFO Starting EventSource {"controller": "groupsync", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GroupSync", "source": "kind source: *v1alpha1.GroupSync"}
1.6921817335677052e+09 INFO Starting Controller {"controller": "groupsync", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GroupSync"}
1.6921817335685656e+09 DEBUG events Normal {"object": {"kind":"Lease","namespace":"group-sync-operator","name":"085c249a.redhat.io","uid":"8ed7b6ef-1f8d-420c-92c0-8277b263df58","apiVersion":"coordination.k8s.io/v1","resourceVersion":"1893983661"}, "reason": "LeaderElection", "message": "group-sync-operator-controller-manager-56f4c64d7-4zg64_0e577929-8a16-4c30-b1c5-a371ec183c1b became leader"}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the sample output in the issue to identify where the operator's log formatting is configured and how controller-runtime and leader-election messages are emitted. Standardize the displayed timestamps to the requested readable format, then verify that all shown message types use it consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100