8d35d0c0fd
Exempt resources from attribute limits ( #1892 )
...
Resources are not susceptible to scenarios where excessive attributes
can be recorded unlike Spans. Resources are also immutable and it can be
hard for some SDKs to apply the limits at source at the time the
attributes are added to a resource. Furthermore, limits and Resources
both are generally defined and passed on to a TracerProvider which
forces a TracerProvider to either mutate the resource or generate a new
one with duplicate attributes in order to apply the limits to it.
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
2023-11-16 12:50:59 -05:00
8c6e0dd69c
Prefer global limit over model-specific default ( #1893 )
2023-11-16 12:50:59 -05:00
2ecdb1f1a2
Add an option to limit length of values of attributes and metric values ( #1130 )
2023-11-16 12:50:59 -05:00
dcf74c311a
Rename Metrics labels to attributes ( #1775 )
2023-11-16 12:50:59 -05:00
71df386e08
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
7a3f37d933
Add lifecycle statuses to all documents ( #1385 )
2023-11-16 12:50:59 -05:00
e8587bacc8
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
1cbb4af73d
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
fb0804ed30
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
01e5a6d827
Include attribute name pluralization guidelines ( #1115 ) ( #1140 )
2023-11-16 12:50:59 -05:00
550a2b904b
Remove ordering reqirement for attributes. ( #1212 )
...
* Remove ordering for attributes.
* Fill in CHANGELOG link
2023-11-16 12:50:59 -05:00
2d55f5436f
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
aa5effe43c
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
a59a1b218c
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
52061e2f52
Fix lint check in makefile, fix errors ( #837 )
...
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
2023-11-16 12:50:59 -05:00
2096cb3ec5
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
795086a9a5
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
19fced8d4f
Consistency between Span and Resource attributes ( #777 )
...
* Consistency between Span and Resource attributes
* Address feedback
* Wording
2023-11-16 12:50:59 -05:00
c82cc039d7
DocFX sanity check ( #742 )
2023-11-16 12:50:59 -05:00
56071a8642
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
4142dd35dd
Renamed `specification` and `semantic_conventions` to `model` and `docs` ( #166 )
2023-07-06 11:43:47 -07:00
902376ef67
Moved resource semconv directly under the resource directory ( #165 )
2023-07-06 10:16:21 -07:00
ded7a09e07
Final restructuring cleanup ( #158 )
2023-07-04 21:15:56 -07:00
37f38fefbb
Restructured messaging semconv ( #146 )
2023-07-03 13:04:08 -07:00
9e8db76488
Restructured feature flag semconv ( #151 )
2023-07-03 10:32:37 -07:00
8690be707a
Moved RPC semantic conventions ( #145 )
2023-07-03 09:34:01 -07:00
676d53a582
Moved FaaS semconv ( #148 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-07-03 17:56:44 +02:00
4011a1ba64
Moved CloudEvents semconv ( #153 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-07-03 17:50:49 +02:00
0238f3a2fe
Moved system metrics semconv ( #154 )
2023-07-03 08:26:13 -07:00
93851b1b20
Moved Exceptions semconv ( #147 )
2023-07-03 08:00:15 -07:00
43d65f3872
Moved `compatibility.md` to general dir ( #152 )
2023-07-01 07:31:46 -07:00
86dacb9a62
Moved database semantic conventions ( #144 )
2023-07-01 07:27:27 -07:00
2d1ea6bb64
Moved general semantic conventions markdown to a topic folder. ( #143 )
2023-06-30 09:20:14 -07:00
afc81230cd
Add YAML definitions for log semantic conventions and define requirement levels ( #133 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-06-30 12:13:12 +02:00
537da5112e
Add semantic conventions for Elasticsearch client instrumentation ( #23 )
...
Co-authored-by: Josh Suereth <joshuasuereth@google.com>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-06-29 16:05:52 +02:00
864359634c
Messaging: Remove `messaging.source.*` attributes ( #100 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-06-29 10:20:37 +02:00
7c1b368cca
Add container semantic conventions resource ( #39 )
...
Co-authored-by: Josh Suereth <joshuasuereth@google.com>
2023-06-28 11:42:25 -04:00
16e611a37b
JVM cpu metrics opt-in ( #57 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-06-28 17:26:37 +02:00
cdaccc8e4a
Moved HTTP semantic conventions to a dedicated topic-based structure ( #141 )
2023-06-28 08:14:15 -07:00
7add90dceb
Mark initial set of HTTP semantic conventions as frozen ( #105 )
2023-06-23 11:49:37 -07:00
29c9b6bc62
Add 'as reported by the JVM' qualifier to JVM cpu metrics ( #115 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-06-23 16:58:22 +02:00
2055854c0c
Change `server.address` and `server.port` from required to recommended on HTTP Server Spans ( #114 )
2023-06-21 16:01:51 -07:00
beb9444651
Mark service.version as stable. ( #106 )
2023-06-20 10:43:49 -07:00
be0fab156d
Limit HTTP request method cardinality: original_method (option A) ( #17 )
2023-06-20 09:20:14 -07:00
156f9424fe
Make server.address and server.port to opt-in on HTTP server metrics ( #109 )
2023-06-19 14:35:45 -07:00
d31b014b1f
Make `url.query` conditionally required for HTTP spans ( #118 )
2023-06-19 10:34:08 -07:00
bef5a68c2f
Recommend emitting server.socket.domain only if it's different from s… ( #94 )
2023-06-14 20:44:04 -07:00
8364aaada5
Split out truly experimental JVM metrics ( #56 )
2023-06-13 20:05:49 -07:00
8f9fbdf8d6
Add `process.runtime.jvm.cpu.time` metric ( #55 )
2023-06-13 17:50:05 -07:00
f07495d905
Add lacking Compute Engine link to the Services section ( #103 )
...
Signed-off-by: Koichi Shiraishi <zchee.io@gmail.com>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Co-authored-by: Josh Suereth <joshuasuereth@google.com>
2023-06-13 13:56:39 -04:00
Owais Lone