Skip to content

Stabilise cpu.mode attributeΒ #3694

Open

Description

@ChrsMark

This issue suggests that we stabilise cpu.mode which is conditionally required for container.cpu.time and hence blocks #3693.

@open-telemetry/semconv-k8s-approvers @open-telemetry/semconv-system-approvers please share your thoughts.

Activity

  1. mx-psi commented on May 4, 2026

    @mx-psi
    Member

    I support this

  2. Dipanshusinghh commented on May 18, 2026

    @Dipanshusinghh
    Contributor

    Hi @ChrsMark, stabilising cpu.mode here seems reasonable, especially since it blocks the broader container.cpu.time stabilization work.
    I hd be interested in helping with the semantic convention updates and reviewing any related enum/documentation consistency if this is available for contribution. Thanks

  3. ChrsMark commented on May 20, 2026

    @ChrsMark
    MemberAuthor

    @Dipanshusinghh what needs to be done here is to promote the attribute to release_candidate as a first step. Feel free to send a PR so as maintainers and approvers can discuss this decision.

  4. Dipanshusinghh commented on May 20, 2026

    @Dipanshusinghh
    Contributor

    Thanks @ChrsMark! I'm currently caught up with an exam, but I'm really keen on working on this. I will start on it and submit the PR by this weekend (in a couple of days).πŸ™πŸΌ

  5. osullivandonal commented on Aug 27, 2026

    @osullivandonal
    Member

    This can be close as this was done in #3739 cc. @ChrsMark @lmolkova

  6. ChrsMark commented on Aug 27, 2026

    @ChrsMark
    MemberAuthor

    Shall we keep it open until it reaches stable? The referenced PR only moved it to release_candidate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions