36ebbcad53
Prefer global limit over model-specific default ( #1893 )
2023-11-16 12:50:59 -05:00
43e0a08c24
Add an option to limit length of values of attributes and metric values ( #1130 )
2023-11-16 12:50:59 -05:00
c37549e1d8
Rename Metrics labels to attributes ( #1775 )
2023-11-16 12:50:59 -05:00
cb6ead3c7a
Clarify usage of "otel." attribute namespace ( #1640 )
...
I noticed developers adding their own attributes to this namespace
without going through the specification. We need to regulate this
namespace through the specification, just like we do it for other
semantic conventions.
2023-11-16 12:50:59 -05:00
8de36bfb30
Add lifecycle statuses to all documents ( #1385 )
2023-11-16 12:50:59 -05:00
4c23074b10
Declare freeze of Trace API Specification 1.0 ( #1121 )
...
* Declare freeze of Trace Specification 1.0
We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).
Resolves https://github.com/open-telemetry/opentelemetry-specification/issues/1120
2023-11-16 12:50:59 -05:00
ba5580577a
Nulls SHOULD NOT be allowed in arrays. ( #1214 )
...
* Nulls SHOULD NOT be allowed in arrays.
* Fill in CHANGELOG link
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-11-16 12:50:59 -05:00
82b14e151c
Add guidance on when to use and not use nested namespaces ( #1197 )
...
This topic has come up at least 3 times now. I believe a clarification is
warranted. The clarification is aligned with previous recommendations:
https://github.com/open-telemetry/opentelemetry-specification/pull/789#issuecomment-675506855
https://github.com/open-telemetry/opentelemetry-specification/pull/882#issuecomment-690945900
https://github.com/open-telemetry/opentelemetry-specification/pull/1194#issuecomment-722431982
2023-11-16 12:50:59 -05:00
501f8a108a
Include attribute name pluralization guidelines ( #1115 ) ( #1140 )
2023-11-16 12:50:59 -05:00
2012c9e386
Remove ordering reqirement for attributes. ( #1212 )
...
* Remove ordering for attributes.
* Fill in CHANGELOG link
2023-11-16 12:50:59 -05:00
9d54f2f42b
Fix absolute links to spec ( #1192 )
...
* Remove absolute links where possible.
* Work around semantic conventions.
* Docfx.
* Fix YAML.
* More docfx.
2023-11-16 12:50:59 -05:00
906beb96fc
Define `null` as an invalid value for attributes and declare attempts to set `null` as undefined behavior ( #992 )
2023-11-16 12:50:59 -05:00
a15b95dafa
Require that names and namespaces are one global space across all semantic convention areas ( #832 )
...
* Require that names and namespaces are one global space across all semantic convention areas
We have semantic conventions for Resources, Spans and Metrics (in the future also Logs are expected).
It was not clear if the attribute names across all convention areas should be globally unique.
This commit asserts that conventions are one space, they are not independent spaces with
their own namespaces each.
We prohibit using the same Span or Resource attribute name or metric label name but give them
slightly different meanings or value sets.
Resolves: https://github.com/open-telemetry/opentelemetry-specification/issues/815
* Address PR comments
Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
2023-11-16 12:50:59 -05:00
15097436c7
Fix lint check in makefile, fix errors ( #837 )
...
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
2023-11-16 12:50:59 -05:00
3fb086c80f
Extend attribute naming rules to metric labels ( #821 )
...
* Extend attribute naming rules to metric labels
We earlier defined naming rules for attributes, however we do not have
similar rules for metric labels. This commit extends the exact same
set of rules to metric labels.
This was brought up in this comment https://github.com/open-telemetry/opentelemetry-specification/pull/807#discussion_r471550053
* Address PR comments
2023-11-16 12:50:59 -05:00
7a01501836
Add conventions for attribute names ( #807 )
...
* Add conventions for attribute names
Resolves: https://github.com/open-telemetry/opentelemetry-specification/issues/726
* Address PR comments
* Re-word company/application specific attribute recommendations
2023-11-16 12:50:59 -05:00
46b79ae1e7
Consistency between Span and Resource attributes ( #777 )
...
* Consistency between Span and Resource attributes
* Address feedback
* Wording
2023-11-16 12:50:59 -05:00
4a2a4ef946
DocFX sanity check ( #742 )
2023-11-16 12:50:59 -05:00
4f5831ca5f
Centralize attributes definition ( #722 )
...
* Centralize attributes definition
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
* Update specification/common/common.md
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* Update specification/common/common.md
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* Update specification/common/common.md
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* Update specification/common/common.md
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* Update specification/common/common.md
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* Update specification/common/common.md
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* Update specification/overview.md
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
2023-11-16 12:50:59 -05:00
b85a0db524
Update spec references to point to local files
2023-11-16 12:50:59 -05:00
1dc1e04ab6
Point to 1.26.0 of specification
2023-11-16 12:50:59 -05:00
f183527bf7
Fix more links
2023-11-16 12:50:59 -05:00
84cd08ef20
Change to relative links
2023-11-16 12:50:59 -05:00
d445ea5eec
Move attribute documents
2023-11-16 12:50:59 -05:00
eece45b83c
Remove files to keep
2023-11-16 12:50:59 -05:00
e56432cc1d
Rename/replace `(client|server).socket.(address|port)` attributes with `network.(peer|local).(address|port)`. ( #3713 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-11-16 12:50:59 -05:00
7ee67a7192
Add a new AddLink() operation to Span. ( #3678 )
...
Fixes #454
Related to #3337
As the Messaging SIG merged its last OTEP 222, we will be adding operations
that require Links after Span creation, taking a direct route with `AddLink()`,
albeit without any of the new members suggested in #3337 , e.g. `timestamp` (to be
discussed in a separate issue).
```
AddLink(spanContext, attributes /* optional */)
```
2023-11-16 12:50:59 -05:00
e3352d43bc
Remove local stubs of semantic conventions. ( #3711 )
2023-11-16 12:50:59 -05:00
9d7cdb9292
Hugo front-matter fixes for aliases and linkTitle ( #3592 )
...
- Followup changes for
https://github.com/open-telemetry/opentelemetry.io/issues/2793
- There are only changes to Hugo front matter
- Adds `likeTitle`s for "Compatibility" pages
- Adds aliases for pages that have moved or were renamed
- Related:
https://github.com/open-telemetry/opentelemetry.io/issues/3013 -- the
`compatibility/openmetrics` spec page is in the list because it was
renamed
/cc @svrnm @cartermp
2023-11-16 12:50:59 -05:00
bd2b51a249
Explain why custom attributes are not recommended to be placed in Otel namespaces ( #3507 )
...
The @open-telemetry/technical-committee discussed and decided to keep the
existing recommendations but clarify them and explain the purpose.
2023-11-16 12:50:59 -05:00
cc85702f85
BREAKING: Introduce common `url.*` attributes, and improve use of namespacing under `http.*` ( #3355 )
2023-11-16 12:50:59 -05:00
d6f3da6f11
BREAKING: Rename remaining network attributes from `net.*` to `network.*` and align definitions with ECS ( #3426 )
2023-11-16 12:50:59 -05:00
1b01442218
BREAKING: Replace `net.peer.*`/`net.host.*` with `client.*`/`server.*` (and `source.*`/`destination.*`) ( #3402 )
2023-11-16 12:50:59 -05:00
f4f8be2cce
Use path, not external URL, for link into glossary ( #3375 )
...
- Contributes to
https://github.com/open-telemetry/opentelemetry.io/issues/2429
- This is part of an effort to normalize links, for improved link
checking on the OTel website
2023-11-16 12:50:59 -05:00
e182ff311d
Mark attribute requirement levels as stable ( #3368 )
2023-11-16 12:50:59 -05:00
4adbc387e9
Clarify that attribute requirement levels apply to instrumentation libraries ( #3289 )
...
Based on discussion in semconv stability WG
Closes #3283
## Changes
Clarifies that attribute requirement levels apply to instrumentation.
And that, because users can transform their telemetry in a number of
ways (e.g. metric views, span processors, and collector
transformations), these requirement levels cannot be relied on by
telemetry consumers.
---------
Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
2023-11-16 12:50:59 -05:00
c717ab4f4c
Attribute requirement level follow-up edits ( #3293 )
2023-11-16 12:50:59 -05:00
8b0bccd2de
Proofread of attribute requirement levels in preparation for stability ( #3270 )
2023-11-16 12:50:59 -05:00
b8e3c86a2b
Rename Optional attribute requirement level to Opt-In ( #3228 )
2023-11-16 12:50:59 -05:00
6b6cba749a
Mark Attribute naming conventions as stable. ( #3220 )
2023-11-16 12:50:59 -05:00
6fb1c444ab
Add log attribute limit configuration ( #2861 )
...
Fixes #2860
Adds log attribute limit configuration.
These new environment variables bring more consistency between spans and logs.
2023-11-16 12:50:59 -05:00
fac9ea093c
Define semantic conventions yaml for non-otlp conventions ( #2850 )
...
* Define semantic conventions yaml for non-otlp conventions
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
* Update semantic_conventions/trace/exporter/exporter.yaml
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* Update semantic_conventions/scope/exporter/exporter.yaml
Co-authored-by: Joao Grassi <joao@joaograssi.com>
* Rename otel to otel_span
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
Co-authored-by: Joao Grassi <joao@joaograssi.com>
2023-11-16 12:50:59 -05:00
8267eacc84
Align log sdk naming with api ( #2768 )
...
Resolves #2752 .
This aligns log SDK and API concepts which have diverged after the merged of #2676 . This PR brings alignment to the log API and SDK, and in brings the log signal into alignment with tracing and metrics where there is conceptual overlap. There shouldn't be any new concepts introduced here.
- Rename `../logs/logging-library-sdk.md` to `../logs/sdk.md`
- Remove wording from SDK that implies that an API doesn't exist, like [this](https://github.com/open-telemetry/opentelemetry-specification/blame/main/specification/logs/logging-library-sdk.md#L60-L62 ).
- Move [How to Create Log4j Style Appender](https://github.com/open-telemetry/opentelemetry-specification/blame/main/specification/logs/logging-library-sdk.md#L219 ) to `api.md` since it describes an API use case.
- Move [Implicit / Explicit Context Injection](https://github.com/open-telemetry/opentelemetry-specification/blame/main/specification/logs/logging-library-sdk.md#L270-L288 ) sections to `api.md` since they describe API level considerations.
- Rename Logger [create](https://github.com/open-telemetry/opentelemetry-specification/blame/main/specification/logs/api.md#L133 ) method to be emit, to align with SDK concept of `LogRecordProcessor#onEmit(..)`.
- Rename `LogProcessor`, `LogExporter` to `LogRecordProcessor`, `LogRecordExporter`.
- Fill in various SDK level TODOs related to shutdown and flushing. The language from these was taken directly from the metrics / tracing SDK - no new concepts were introduced.
2023-11-16 12:50:59 -05:00
a181cc323e
Define net.sock attributes and clarify logical net.peer|host.name attributes ( #2614 )
2023-11-16 12:50:59 -05:00
fe3cf1830c
Add note to Hugo front matter ( #2651 )
2023-11-16 12:50:59 -05:00
aafd53c129
Use consistent file name for data-model.md ( #2586 )
2023-11-16 12:50:59 -05:00
b0047edbc3
Introduce Instrumentation Scope Attributes ( #2579 )
2023-11-16 12:50:59 -05:00
fb860bc667
Move non-otlp.md to common directory ( #2587 )
2023-11-16 12:50:59 -05:00
a1f9af0259
Add missing READMEs to section ( #2559 )
2023-11-16 12:50:59 -05:00
b8926d2db9
Define attribute requirement levels ( #2522 )
...
* nits
* review comments
* No exceptions for Required attributes, clarifications on performance
* Conditional clarifications
* nits
* Conditional -> required conditionally and minor fixes
* Align requirement levels with RFC levels better
* Clarify Note on required attributes
* Update specification/common/attribute-requirement-level.md
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
* Clarify Note on required attributes
* Remove performance from conditionally required attributes
* Clarify Conditionally Required case when condition is false
* Apply suggestions from code review
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
* Apply suggestions from code review
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
* headings for levels and moving things around
* nits: formatting
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
Co-authored-by: Reiley Yang <reyang@microsoft.com>
2023-11-16 12:50:59 -05:00
Owais Lone