c7c60cae12
Expand pool.name in semantic conventions ( #3050 )
...
according to the discussion here:
https://github.com/open-telemetry/opentelemetry-specification/issues/3038
I'm updating the `pool.name attribute`
2023-03-03 10:59:56 -06:00
c9ff781e94
Make net.sock.host.port conditionally required ( #3246 )
2023-03-02 14:01:52 -08:00
6d7b233c80
Rename http.user_agent to user_agent.original ( #3190 )
...
Fixes #3180
## Changes
Renames `http.user_agent` to `user_agent.original`.
2023-03-02 14:47:29 -06:00
47cabcf799
Rename Optional attribute requirement level to Opt-In ( #3228 )
2023-03-01 15:13:24 -08:00
f839f1ed9a
clarify how to collect host.id for non-containerized systems ( #3173 )
2023-02-28 18:17:04 +01:00
90a7dae56c
Remove mention of net.transport from http semantic conventions ( #3244 )
...
Based on @lmolkova's
https://github.com/open-telemetry/opentelemetry-specification/issues/3215#issuecomment-1439068151
## Changes
Removes mention of `net.transport` from http semantic conventions.
---------
Co-authored-by: Reiley Yang <reyang@microsoft.com>
2023-02-28 10:52:04 -05:00
e9d9309590
Update build-tools to 1.16.0 ( #3259 )
...
build-tools 1.16.0 was just released and is necessary to unblock
https://github.com/open-telemetry/opentelemetry-specification/pull/3190
2023-02-27 17:39:23 -05:00
2447fb063f
Expand scope of `faas.id` to `cloud.resource_id` ( #3188 )
...
## Changes
As per the discussion on #3188 , we determined it is better to move
rather than remove as this attribute is still important for some systems
despite it containing duplicated information.
2023-02-27 12:13:13 -06:00
12481fef89
add semantic conventions for heroku ( #3075 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-02-27 10:23:29 +01:00
a0691c65ed
Rename nonheap to non_heap ( #3250 )
...
Fixes
https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/7876
(the implementation used `non_heap`, which seems better)
## Changes
Renames JVM metric attribute value from `nonheap` to `non_heap`.
---------
Co-authored-by: Carlos Alberto Cortez <calberto.cortez@gmail.com>
2023-02-24 09:59:43 -06:00
85ec713c1c
Metric requirement levels ( #3237 )
2023-02-23 08:22:54 -08:00
0f2a834cda
Add Connect RPC to semantic conventions ( #3116 )
...
* Add connect_rpc to rpc.yaml
* Add connect rpc into rpc-metrics and rpc markdown
* Add Connect RPC change to CHANGELOG.md
* Update CHANGELOG.md
---------
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-02-21 09:50:35 -05:00
0d0b9d0a7d
Rename `faas.execution` to `faas.invocation_id` and change units for `faas.max_memory` ( #3209 )
2023-02-20 09:29:24 -06:00
1971550982
[editorial] Fix Tencent Cloud link ( #3231 )
2023-02-20 10:29:04 +01:00
702cf2cdf3
Rename Logs API to Logs Bridge API to prevent confusion ( #3197 )
...
We keep seeing confusion about what Logs API is. There was a proposal [1]
to use the term Bridge API to help prevent the confusion.
Please take a look and comment on whether you think this renaming helps
and is reasonable.
[1] https://github.com/open-telemetry/opentelemetry-specification/pull/3187#issuecomment-1424431424
2023-02-16 14:55:56 -05:00
6086a26696
Update exceptions.md ( #3217 )
2023-02-16 05:42:42 -06:00
8290599ccd
Get rid of double negation in Events semantic conventions ( #3159 )
...
* getting rid of double negation
* Update specification/logs/semantic_conventions/events.md
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
---------
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
2023-02-15 14:56:19 -05:00
a0f96da61f
Fix rpc examples to include grpc namespace ( #3211 )
2023-02-15 09:12:30 -08:00
3a0a197f4c
Use attribute_group for cross-signal HTTP attributes ( #3183 )
2023-02-13 16:00:14 -08:00
30ef366d8a
Update aws lambda spec to remove X-Ray Env propagation ( #3166 )
...
* Update aws lambda spec to remove X-Ray Env propagation
Per discussion in the FAAS SIG, we decided that the aws x-ray environment variable should be moved to a span link to avoid interfering with the configured propagators.
2023-02-10 10:57:34 -06:00
1781e9270e
Add 1.1.8.0 Schema. ( #3175 )
2023-02-07 13:01:58 -06:00
2165c692f9
Http route should contain application root ( #3164 )
2023-02-06 12:50:01 -08:00
27e087b3b6
Add http metrics yaml ( #3158 )
...
* Add http metrics yaml
* Update change log
* Fix notes
* Fix link
* Remove unnecessary field
2023-02-06 12:54:51 -05:00
9170ccaeeb
Changes to http span name ( #3165 )
2023-02-03 08:33:10 -08:00
912809fb42
Enable semantic convention tooling for metrics ( #3119 )
2023-01-24 08:52:53 -08:00
e35ad2b9d5
[semantic_conventions/resource] fix google platform openshift naming ( #3095 )
2023-01-23 14:56:48 -08:00
b45d32f1ed
Add cloud spanner and mssql compact to db specifications ( #3105 )
2023-01-23 16:18:51 -06:00
ebcf353c33
Remove rogue bracket ( #3108 )
2023-01-17 09:54:55 -08:00
54ca902e06
Update the 1.17 Schema to reference the proper changes PR ( #3099 )
2023-01-12 20:01:16 -06:00
708df51809
Add ClickHouse in the database group ( #3011 )
2023-01-03 19:40:09 -06:00
4de43114a4
Suggest column # as an extra source code attribute ( #3029 )
2023-01-02 18:01:32 -06:00
a7ede6fbfa
Refactor messaging attributes and specify per-message attributes ( #2957 )
2022-12-22 17:04:53 -06:00
41f5b5508b
Clarify common HTTP attributes apply to both clients and servers ( #3044 )
2022-12-16 21:48:49 +01:00
90a6aeee14
[editorial] Metrics hardware sem. conv. front matter ( #3045 )
2022-12-16 13:17:23 -06:00
3f3308305b
Add 1.16.0 Schema. ( #3016 )
2022-12-08 00:37:22 +01:00
656644592a
[resource] add openshift platform to all supported cloud providers ( #2985 )
2022-12-06 16:52:30 +01:00
0204860d46
Update semconv for hardware metrics to use `direction` attributes ( #2942 )
2022-12-06 00:17:54 +01:00
0adf032cf1
Add feature flagging semantic conventions ( #2529 )
2022-12-01 12:13:48 -08:00
e37e300610
Add `messaging.kafka.message.offset` attribute ( #2982 )
2022-12-01 19:21:38 +01:00
84bc1e50fc
Fix net peer name IP example address ( #2995 )
2022-12-01 18:38:24 +01:00
6f0cadac7e
List the machine-id as potential source for a unique host.id ( #2978 )
2022-11-29 10:06:04 -08:00
fa6cef115c
Rename grpc metadata attribute names to reflect that they are grpc-specific ( #2981 )
2022-11-22 15:53:34 -08:00
b901d9dd76
add ibm cloud as a cloud provider ( #2965 )
2022-11-21 10:31:32 -08:00
f517f6b17b
Make http.status_code an int ( #2943 )
2022-11-17 13:33:59 -08:00
fce78ebfc5
Move Prometheus/OpenMetrics compatibility to its own file ( #2952 )
2022-11-17 13:22:10 -08:00
43804f56d2
Track JVM gc time in histogram ( #2903 )
2022-11-15 12:53:05 -08:00
0644776443
Split out Event API from Log API ( #2941 )
...
Resolves #2917 .
Depends on #2940 .
2022-11-14 18:07:56 -05:00
acb0d5db18
Move event.domain from InstrumentationScope to LogRecord ( #2940 )
...
Resolves #2939 .
2022-11-14 10:34:49 -05:00
b334f6b070
Clarification on what an Event is, and what the event.domain and event.name attributes represent ( #2848 )
...
* Remove language around uniqueness of event names within a domain
This came up in
https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/14474
where it was highlighted that just `name` is not sufficient to provide
for uniqueness of a Kubernetes Event.
The attribute `event.domain` is only meant to be a logical separation
across different event systems, so it allows for similar looking names
in different domains but with a completely different purpose. However,
within each domain we don't have to have any uniqueness constraints on
the `name` and leave it to whatever is idiomatic to the particular event
system the domain represents.
2022-11-09 14:01:28 -05:00
07ef735d2f
s/cpu/CPU ( #2931 )
...
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
2022-11-09 17:10:44 +01:00
Haddas Bronfman