132fd6aa14
* Clarify that Trace/Meter are associated with Instrumentation Scope This is a slightly different take on https://github.com/open-telemetry/opentelemetry-specification/issues/2203 Instead of renaming instrumentation library to instrumentation scope everywhere this PR suggests targetted editing of wording of the Trace/Meter obtaining API to allow not just instrumentation library but other instrumentation scopes to be used as a parameter. This change does not force renaming of API parameters and is not a breaking change. We consider it a clarification of usage to match the intent that we had for the "name" field. If this PR is accepted there will be a follow up PR that will suggest to rename InstrumentationLibrary* messages in OTLP proto to InstrumentationScope* message. Such a change will not be a breaking change for the OTLP wire format and is acceptable. If this PR is accepted we will also close https://github.com/open-telemetry/opentelemetry-specification/pull/1236 since it will be no longer necessary. The logger name will be recorded as the instrumentation scope. This clarification will be a follow up PR that clarifies the behavior in https://github.com/open-telemetry/oteps/blob/main/text/logs/0150-logging-library-sdk.md |
||
|---|---|---|
| .github | ||
| .vscode | ||
| docs | ||
| internal/tools | ||
| model | ||
| schemas | ||
| specification/common | ||
| supplementary-guidelines/compatibility | ||
| .gitattributes | ||
| .gitignore | ||
| .markdown_link_check_config.json | ||
| .markdownlint.yaml | ||
| .nvmrc | ||
| .prettierignore | ||
| .yamllint | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| docfx.json | ||
| gulpfile.js | ||
| package.json | ||
| schema-next.yaml | ||
README.md
OpenTelemetry Semantic Conventions
Welcome to the new repository!
This is currently a direct copy/filter-branch of the Specification repository with only semantic conventions included.
This repository is currently using this specification version.
Read the docs
The documentation currently resides in the docs folder.
Contributing
See CONTRIBUTING.md
Approvers (@open-telemetry/specs-semconv-approvers):
- Christian Neumüller, Dynatrace
- James Moessis, Atlassian
- Johannes Tax, Grafana Labs
- Liudmila Molkova, Microsoft
- Sean Marciniak, Atlassian
- Ted Young, Lightstep
Find more about the approver role in community repository.
Maintainers (@open-telemetry/specs-semconv-maintainers):
- Alexander Wert, Elastic
- Armin Ruech, Dynatrace
- Joao Grassi, Dynatrace
- Josh Suereth, Google
- Reiley Yang, Microsoft
Find more about the maintainer role in community repository.