Improve Observability

[zarvd]

Problems:

Logging:

• mixed-use plain-text logging and structural logging
• coverage
• convention

Goals

scope: logging/metrics/tracing

• standardize convention and improve the coding experience
• improve debug efficiency

Refs

Logging:

• https://github.com/kubernetes-sigs/controller-runtime/blob/master/TMP-LOGGING.md
• https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md
• https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/migration-to-structured-logging.md

To-do

Logging

• Adopt structural logging
• Adopt logr interface
• Adopt JSON format? (easy to parse)

TBD: require discussion?

Tracking Tasks

• [ ] logging
  • [ ] a demo / mvp https://github.com/kubernetes-sigs/cloud-provider-azure/pull/1494
  • [ ] refactor others

[ZombieMInd]

Why is https://github.com/kubernetes-sigs/cloud-provider-azure/pull/1494 closed? Does this issue require another approach?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Sajiyah-Salat]

is this pr still valid?