Define standard, vendor-agnostic, language-agnostic instrumentation identity attributes

[michaelsafyan]

Changes

Introduces instrumentation.source.* and instrumentation.distribution.* attributes to enable more triangulation of dependency libraries that have been instrumented with Open Telemetry and that construct the InstrumentationScope.

This is forked off from related pull request:

• Propose semantic conventions for GCP client library identification #1047

The related pull request includes GCP-specific attributes (e.g. gcp.client.service). Standard, common attributes were requested there. This pull request aims to provide the general, vendor-agnostic attributes requested.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions.

[joaopgrassi]

It almost seems like we need general conventions to define packages, package repositories and source code 🤔 .

[joaopgrassi]

We discussed this PR in the semantic conventions meeting (2024-06-17). Basically, we see the following issues/points to clarify:

• Several attributes seem similar/relevant to CI/CD for example, target, repo. We can see those also being use there
• Other attributes look like they also describe a general concept of a "package", like the name of the package, where one can find it.
• Potential conflicts with scope name,version and artifact name/version

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[lmolkova]

Related: #1229

[pellared]

Related: open-telemetry/opentelemetry-specification#4146

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.