Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

2021 Annual Report: SIG Instrumentation

Current initiatives

  1. What work did the SIG do this year that should be highlighted?

    • Formed WG Structured Logging. Successfully migrated multiple components to structured logs and graduated feature to beta.
    • Added tracing support to the Kubernetes API server and began work on Kubelet tracing.
    • Graduated the metrics stability framework.
  2. What initiatives are you working on that aren't being tracked in KEPs?

    • Bi-weekly triage meeting
    • Subprojects (see below)
  3. KEP work in 2021 (1.x, 1.y, 1.z):

Project health

  1. What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details)

  2. What metrics/community health stats does your group care about and/or measure?

    • Devstats
    • Meeting attendance
      • Meeting attendance is ~10 each week
      • Triage attendance is ~5 each week
    • Enhancement velocity
      • 7 Active enhancements over the year
  3. Does your help new contributors engage with your group specifically by pointing to activities or programs that provide useful context or allow easy participation?

    • We don't have our own as the overall one is suitable for our SIG. However, we have filed an issue to create one to better document how to get involved with our subprojects.
  4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general contributor guide, does your document those to help existing contributors grow throughout the contributor ladder?

    • N/A, we don't have special training or requirements
  5. Does the group have contributors from multiple companies/affiliations?

    • Yes: Google, Red Hat, Sony, VMware, Intel, independent contributors, and more
  6. Are there ways end users/companies can contribute that they currently are not? If one of those ways is more full time support, what would they work on and why?

SIG leads performed a staffing and gap analysis for the SIG's projects. We definitely can use more help, and need more part-time/full-time contributors.


  • KTLO: 4 leads at 5%, 2 maintainers at 10% for core, 9-10 maintainers at 5% for 5 subprojects (can have overlap between roles, but need a minimum of 3-4 part-time contributors at 25%)
  • Feature work: needs significant ongoing additional investment, minimum of 2-3 FT devs or features will continue to slip


  • KTLO: Requires two experienced part-time maintainers at 10% (e.g. 2x4h = 8h/wk) in addition to the SIG leadership (chairs/TLs @ minimum of 2h/wk)
    • Chairs/TLs currently perform the bulk of this work but even amongst the four of them, do not have 8h total weekly allocated
  • Feature work: requires significantly more investment from development and review time.


  • Subprojects are currently mature/stable and mainly have KTLO needs
  • kube-state-metrics: 2-3 experienced maintainers at 5%, currently staffed
  • Metrics-server: 2 experienced maintainers at 5%, currently staffed
  • Custom-metrics-apiserver: 1 experienced maintainer at 5%, currently staffed
  • Klog: 2 experienced maintainers at 5%, has no current staffing
  • Prometheus-adapter: 2 experienced maintainers at 5%, has no current staffing


  • Primary slack channel member count: 1,740
  • Primary mailing list member count: 324
  • Primary meeting attendee count (estimated, if needed): 8-12
  • Primary meeting participant count (estimated, if needed): 4-6
  • Unique reviewers for SIG-owned packages: 24
  • Unique approvers for SIG-owned packages: 22

Include any other ways you measure group membership

  • We track active members in the SIG primarily based on devstats and meeting participation, and maintain an up-to-date roster of members in kubernetes/org. These teams also serve as aliases for GitHub pings.


New in 2021:

Retired in 2021:


Working groups

New in 2021:


Operational tasks in