wg-structured-logging: annual report 2024
This commit is contained in:
parent
d1b3d78d26
commit
8c4310161b
|
@ -5,29 +5,35 @@
|
||||||
|
|
||||||
1. What work did the WG do this year that should be highlighted?
|
1. What work did the WG do this year that should be highlighted?
|
||||||
|
|
||||||
<!--
|
Conversion of some additional components to structured, contextual logging
|
||||||
Some example items that might be worth highlighting:
|
proceeded, most notably in the kubelet. [Contextual
|
||||||
- artifacts
|
logging](https://github.com/kubernetes/enhancements/issues/3077) got promoted
|
||||||
- reports
|
to beta in Kubernetes 1.30.
|
||||||
- white papers
|
|
||||||
- work not tracked in KEPs
|
Lack of support for contextual logging in client-go leads to a significant
|
||||||
-->
|
amount of log entries without context or not even using unstructured logging,
|
||||||
|
[sometimes lacking information](https://github.com/kubernetes/klog/issues/414)
|
||||||
|
that would identify which component the log message is about.
|
||||||
|
|
||||||
|
The focus end of 2024 was on [addressing that gap in
|
||||||
|
client-go](https://github.com/kubernetes/kubernetes/pull/129125), with
|
||||||
|
hopefully all changes landing in Kubernetes 1.34 in 2025.
|
||||||
|
|
||||||
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
|
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
|
||||||
|
|
||||||
|
Once client-go is updated, we need to revisit components that were already
|
||||||
|
converted and make them use the new client-go APIs.
|
||||||
|
|
||||||
## Operational
|
## Operational
|
||||||
|
|
||||||
Operational tasks in [wg-governance.md]:
|
Operational tasks in [wg-governance.md]:
|
||||||
|
|
||||||
- [ ] [README.md] reviewed for accuracy and updated if needed
|
- [x] [README.md] reviewed for accuracy and updated if needed
|
||||||
- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed
|
- [x] WG leaders in [sigs.yaml] are accurate and active, and updated if needed
|
||||||
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed
|
- [ ] Meeting notes and recordings for 2024 are linked from [README.md] and updated/uploaded if needed:
|
||||||
- [ ] Updates provided to sponsoring SIGs in 2024
|
regular meetings continue to be on hold, we discuss topics ad-hoc on Slack
|
||||||
- [$sig-name](https://git.k8s.io/community/$sig-id/)
|
- [x] Updates provided to sponsoring SIGs in 2024
|
||||||
- links to email, meeting notes, slides, or recordings, etc
|
- KubeCon EU 2024 maintainer track presentation: ["Leverage Contextual and Structured Logging in K8s for Enhanced Monitoring"](https://kccnceu2024.sched.com/event/1YhhM/leverage-contextual-and-structured-logging-in-k8s-for-enhanced-monitoring-patrick-ohly-intel-gmbh-shivanshu-raj-shrivastava-independent-mengjiao-liu-daocloud)
|
||||||
- [$sig-name](https://git.k8s.io/community/$sig-id/)
|
|
||||||
- links to email, meeting notes, slides, or recordings, etc
|
|
||||||
-
|
|
||||||
|
|
||||||
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
|
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
|
||||||
[README.md]: https://git.k8s.io/community/wg-structured-logging/README.md
|
[README.md]: https://git.k8s.io/community/wg-structured-logging/README.md
|
||||||
|
|
Loading…
Reference in New Issue