f51df2fdbc
Define messaging metrics and add `error.type` attribute to spans ( #163 )
2023-11-30 17:06:23 +01:00
efd9345199
feat: Add MySQL instance address attribute ( #345 )
...
Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
2023-11-30 09:22:16 +01:00
fc73453d04
Expanding k8s.pod resource to include pod labels ( #494 )
...
Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
2023-11-27 09:01:28 +01:00
fe200c01bc
Fix links still pointing to spec repo main branch ( #556 )
2023-11-24 14:37:17 +01:00
0c6d5e1e5a
Improve visibility of used spec version in the semconv repo ( #558 )
...
Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
2023-11-24 14:08:44 +01:00
12dfe6a321
Merging events domain and name ( #473 )
...
Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com>
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
Co-authored-by: jack-berg <34418638+jack-berg@users.noreply.github.com>
Co-authored-by: Joao Grassi <joao.grassi@dynatrace.com>
Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
2023-11-24 12:34:00 +01:00
9d9990cfe8
Add registry md file for disk attributes ( #555 )
...
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
2023-11-23 12:24:22 +01:00
b56abb47df
Remove Oct 1 mention from `OTEL_SEMCONV_STABILITY_OPT_IN` ( #541 )
...
Co-authored-by: Joao Grassi <joao.grassi@dynatrace.com>
Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
2023-11-22 17:25:27 +01:00
34cc9485be
system: shared IO direction attributes ( #530 )
...
Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
2023-11-22 11:25:58 +01:00
04c8e49dc4
Use new partition attribute path ( #547 )
2023-11-21 13:58:45 +01:00
126059d99d
Rename metrics `jvm.memory.usage` to `jvm.memory.used` and `jvm.memory.usage_after_last_gc` to `jvm.memory.used_after_last_gc` ( #536 )
...
Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
Co-authored-by: Joao Grassi <joao.grassi@dynatrace.com>
2023-11-20 16:45:22 +01:00
dccfffc9bf
docs(messaging): add gcp_pubsub ordering key attribute ( #528 )
...
Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
2023-11-19 11:06:31 +01:00
b5b1e6a020
[CI] Run checks.yml on all branches ( #540 )
2023-11-17 16:45:33 +01:00
8962dbeeda
Remove misleading pluralization wording related to count metrics ( #488 )
...
Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
2023-11-17 09:57:45 +01:00
811dbab22a
Moved database attributes to the attributes registry ( #441 )
...
Signed-off-by: Alexander Wert <alexander.wert@elastic.co>
Co-authored-by: Joao Grassi <joao.grassi@dynatrace.com>
Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
2023-11-17 09:46:57 +01:00
48d3348fea
Format with prettier
2023-11-16 12:50:59 -05:00
55f5ce9a0c
Move attribute documents
2023-11-16 12:50:59 -05:00
7e251196c9
Remove files to keep
2023-11-16 12:50:59 -05:00
04d784279e
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
c0513fbd99
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
0b3465ca3d
Remove local stubs of semantic conventions. ( #3711 )
2023-11-16 12:50:59 -05:00
2af3a419d3
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
db45b8950c
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
92a7f35fc0
BREAKING: Introduce common `url.*` attributes, and improve use of namespacing under `http.*` ( #3355 )
2023-11-16 12:50:59 -05:00
70ffed7002
BREAKING: Rename remaining network attributes from `net.*` to `network.*` and align definitions with ECS ( #3426 )
2023-11-16 12:50:59 -05:00
3d4e7b452a
BREAKING: Replace `net.peer.*`/`net.host.*` with `client.*`/`server.*` (and `source.*`/`destination.*`) ( #3402 )
2023-11-16 12:50:59 -05:00
079ef0c249
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
899a24adb1
Mark attribute requirement levels as stable ( #3368 )
2023-11-16 12:50:59 -05:00
eadd2af3a1
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
b5f419fee3
Attribute requirement level follow-up edits ( #3293 )
2023-11-16 12:50:59 -05:00
dba3c1c9a3
Proofread of attribute requirement levels in preparation for stability ( #3270 )
2023-11-16 12:50:59 -05:00
58c415c1ba
Rename Optional attribute requirement level to Opt-In ( #3228 )
2023-11-16 12:50:59 -05:00
35e27bcb99
Mark Attribute naming conventions as stable. ( #3220 )
2023-11-16 12:50:59 -05:00
99f6917344
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
d1eb5e2e74
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
3fd804bd85
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
5f11d9f4f7
Define net.sock attributes and clarify logical net.peer|host.name attributes ( #2614 )
2023-11-16 12:50:59 -05:00
6cd2374786
Add note to Hugo front matter ( #2651 )
2023-11-16 12:50:59 -05:00
894b49059b
Use consistent file name for data-model.md ( #2586 )
2023-11-16 12:50:59 -05:00
e67da74c1f
Introduce Instrumentation Scope Attributes ( #2579 )
2023-11-16 12:50:59 -05:00
9eaea0af14
Move non-otlp.md to common directory ( #2587 )
2023-11-16 12:50:59 -05:00
8781d7df05
Add missing READMEs to section ( #2559 )
2023-11-16 12:50:59 -05:00
3767588666
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
97d6ebffcc
Ensure common section has a README ( #2479 )
2023-11-16 12:50:59 -05:00
b5306f3db2
Implement OTEP 0178: Mapping external data to AnyValue ( #2385 )
...
OTEP 0178 [0] proposed this mapping. This PR merges the proposal into specification.
The content of this PR is mostly copy/paste of the text of the OTEP minus the
irrelevant sections such as "Alternates", etc.
0 - https://github.com/open-telemetry/oteps/blob/main/text/0178-mapping-to-otlp-anyvalue.md
2023-11-16 12:50:59 -05:00
ec4cee89ae
Fix links ( #2426 )
2023-11-16 12:50:59 -05:00
5f93caf5bb
Describe how to convert non-string primitives for protocols which only support strings ( #2343 )
...
* Describe how to handle converting non-string primitives for protocols that only support strings
* update wording to make clear that only non-string values are converted to strings
* unify language
* Update specification/common/common.md
Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>
Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>
Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
2023-11-16 12:50:59 -05:00
132fd6aa14
Clarify that Trace/Meter are associated with Instrumentation Scope ( #2276 )
...
* 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
2023-11-16 12:50:59 -05:00
c948e38726
Clarify that attribute keys are unique in collections ( #2248 )
...
Attributes keys must be unique. The key/value pair collections in the specification
was always intended to model a map.
There was a recent confusion about this. This change clarifies the spec.
Resolves https://github.com/open-telemetry/opentelemetry-specification/issues/2245
2023-11-16 12:50:59 -05:00
22b6b073e3
Prohibit usage of retired names in semantic conventions ( #2191 )
...
* Prohibit usage of retired names in semantic conventions
This change adds a prohibition clause that requires that no old
metric or attribute name is used for a new attribute.
This is important to ensure reversibility of schema transformation
(converting from a new version to an old version of schema).
Without this restriction the following is possible:
Schema version 1. Attribute A exists.
Schema version 2. Attribute A is renamed to B. Appropriate schema file is created.
Schema version 3. Attribute A is introduced (a completely different new attribute).
Now attempting to go from Version 3 to version 1 is impossible since it requires
renaming B to A (for the change in version 2), but a different attribute A already exists.
* Fix based on comments
* Add changelog entry
Co-authored-by: Carlos Alberto Cortez <calberto.cortez@gmail.com>
2023-11-16 12:50:59 -05:00
Liudmila Molkova