Ownership / Cost Centre Conventions

[agardnerIT]

I believe it would be valuable to add ownership information across most / all resource types in the OTEL semantic conventions.

With this, I could signal the "Adam owns host X" or "Team X owns namespace foo".

Same goes with cost centre: "Team Y should be charged for these clusters"

[smith]

In many organizations using cloud providers this is expressed as a set of attributes. From the internal docs where I work:

Keys requirements are:
= The value will be from an allowed list of values which are mentioned here
= The value will be from an allowed list of values which are mentioned here
= The team you are on
= The project you are working on

Example:
division: engineering
org: engprod
team: ci
project: buildkite

(I don't think this example is what the convention's attributes should be, just an example to show variation in how organizations express ownership.)