Skip to content

Process semconv: define common attributes and revisit requirement levelsΒ #864

Closed

Description

@lmolkova

Area(s)

area:process

Is your change request related to a problem? Please describe.

We require any of the following attributes to be present

**Additional attribute requirements:** At least one of the following sets of attributes is required:
* [`process.executable.name`](../attributes-registry/process.md)
* [`process.executable.path`](../attributes-registry/process.md)
* [`process.command`](../attributes-registry/process.md)
* [`process.command_line`](../attributes-registry/process.md)
* [`process.command_args`](../attributes-registry/process.md)

As a result, users would get inconsistent data from different systems and instrumentations.
Vendors will need to know how to parse and extract specific details (such as process name).

Describe the solution you'd like

The approach we follow in HTTP and other semconv:

  • Find 1-2 required attributes (e.g. process.executable.name) which are available everywhere
  • Require instrumentations to do the parsing/extraction of this common information so that users and consumers would get consistent data
  • Set appropriate requirement levels on other attributes

Activity

  1. ChrsMark commented on Apr 8, 2024

    @ChrsMark
    Member

    cc: @open-telemetry/semconv-system-approvers

  2. mx-psi commented on Dec 12, 2024

    @mx-psi
    Member

    Discussed on 2024-12-12 System SemConv WG meeting. We can take care of this as part of defining processes as Entities. The place to put this information down as YAML is not ready yet but we can work on this in parallel.

    @dmitryax has a doc where we are working on this. He will create an issue for defining processes as an entitity and mark this as blocked on that issue.

  3. mx-psi commented on Jan 16, 2025

    @mx-psi
    Member

    @/dmitryax has a doc where we are working on this. He will create an issue for defining processes as an entitity and mark this as blocked on that issue.

    See #1751, marking this as blocked

  4. ChrsMark commented on Oct 2, 2025

    @ChrsMark
    Member

    I think that's also related to #626 which was discussed in the past.

  5. moved this from Blocked to In Progress in System Semantic Convention Working Groupon Oct 23, 2025
  6. osullivandonal commented on Feb 6, 2026

    @osullivandonal
    Member

    Just looking at this, correct me if I am wrong, we need to update our process common attributes and make some required. For example, this would mean making process.executable.name required instead of conditionally_required. The idea is we want to make a few attributes required that are consistently available across all platforms, for example, process.executable.name should be available across, Linux, Windows, and Darwin.

    The collector-contrib hostmetrics receiver already provides this attribute by default, but the question is: how would other instrumentations in language SDKs need to change with this update? Looking at the opentelemtry-go sdk, this is not enabled by default, see here.

    Happy to help here and open a draft PR if that works? cc. @braydonk

  7. braydonk commented on Feb 6, 2026

    @braydonk
    Member

    Thanks @osullivandonal, my PR #3107 should pretty much cover this issue but I need to go back and reopen it addressing the comments.

  8. ChrsMark commented on Feb 10, 2026

    @ChrsMark
    Member

    @braydonk @osullivandonal just double checking on this since I'm a bit confused about the current state πŸ˜… .

    The original description of this issue is about revisiting the requirement levels of the following:

    **Additional attribute requirements:** At least one of the following sets of attributes is required:
    * [`process.executable.name`](../attributes-registry/process.md)
    * [`process.executable.path`](../attributes-registry/process.md)
    * [`process.command`](../attributes-registry/process.md)
    * [`process.command_line`](../attributes-registry/process.md)
    * [`process.command_args`](../attributes-registry/process.md)

    However the mentioned PR doesn't seem to change any of those but rather set the requirement level for a few others.

    Can we clarify if #3107 is the only thing missing and update this issue accordingly?

    It seems that the current issue is the only blocker for promoting process.* to release_candidate based on #3041, which is something we can target soon hopefully before KubeConEU (26') :) .

  9. ChrsMark commented on Feb 12, 2026

    @ChrsMark
    Member

    It turns out we have 2 different issues to cover. One is to revisit Process Entity and its attributes and the second is to cover metrics' attributes and their requirement levels. See #3041 (comment).

  10. mx-psi commented on Mar 25, 2026

    @mx-psi
    Member

    This was fixed by #3461 and #3548

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

Metadata

Metadata

Assignees

Type

No type

Fields

Priority

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions