Open sftim opened 3 years ago
/area logging /triage accepted /cc @serathius
@ehashman: The label(s) area/logging
cannot be applied, because the repository doesn't have them.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
/lifecycle frozen
@sftim, so this issue is only aimed at adding a page in k8s.dev which will contain the content of this page?
Or do we have to change the content of (https://kubernetes.io/docs/concepts/cluster-administration/system-logs/#structured-logging) this page too?
Because this is a migration, we would also modify https://kubernetes.io/docs/concepts/cluster-administration/system-logs/#structured-logging to omit the migrated content, and also to link to the new page.
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
/triage accepted
(org members only)/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
/triage accepted /assign @pohly @serathius
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
/triage accepted
(org members only)/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
/triage accepted
What would you like to be migrated
Why is this needed https://kubernetes.io/docs/concepts/cluster-administration/system-logs/#structured-logging is mostly aimed at Kubernetes contributors, not cluster operators. Documentation for contributors should live within https://k8s.dev/
Comments /sig instrumentation /sig contributor-experience