13e82eae88
erlang/elixir: add stacktrace representation to table ( #3313 )
...
Adds the functions to use for stacktrace representation in Erlang/Elixir
to the semantic conventions table for exceptions.
2023-03-24 12:05:38 -06:00
efa4181f83
Added AWS S3 semantic conventions ( #3251 )
2023-03-22 08:29:16 -07:00
006e3b4091
Add Cosmosdb attributes for open telemetry ( #3097 )
2023-03-21 10:49:17 -07:00
139842c9e0
BREAKING: remove messaging.destination.kind and messaging.source.kind values ( #3214 )
...
Fixes #3170 , #3265 , #3249
## Changes
~~We currently allow `topic` or `queue` on `messaging.destination.kind`.
While it's common in messaging world to have one or another, messaging
semantic conventions can be applied to AMPQ communication (which does
not have topic/queue terminology), [socket.io](https://socket.io/ ), and
potentially other less traditional messaging use-cases.~~
It's unclear how `messaging.destination.kind` and
`messaging.source.kind` could be used. The distinction between queue and
topic is significant for messaging and distributed systems, but not for
tracing.
In either case, tracing backends should expect to process traces from 0+
messaging and 0+ messaging consumers. In either case, message consumers
can be simultaneous or consequent and there could be many of them.
The only known case (Solace) where it could be useful is when messaging
system allows having queues and topic with the same name on the same
broker, and it could be used to distinguish one from another.
Based on messaging SIG discussion, the attributes are removed for the
time being until we understand if and how they are useful.
Depending on messaging system queues or topics behavior vary a lot and
in future it would makes more sense to represent actual behavior with
individual attributes such as:
- auto-settlement (at-most-once or at least once guarantees)
- settlement for individual messages or offsets
- broadcast or unicast
- etc
2023-03-21 10:51:55 -06:00
b7e8b54419
BREAKING rename `net.app.protocol.(name|version)` to `net.protocol.(name|version)` and replace `http.flavor` with `net.protocol.(name|version)` ( #3272 )
2023-03-10 10:15:15 -08:00
40a91717ba
Show relationship between http target and route in example usage ( #3292 )
...
## Changes
Clarify relationship between `http.target` and `http.route` by using the
same pattern in the example usage. Having different patterns for the
attribute values distorts the relationship between the two attributes.
A similar pattern is seen in the docs for
[`aws-lambda.md`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/instrumentation/aws-lambda.md#api-gateway-request-proxy-lambda-tracing-passive ),
where `http.target` is `/pets/10` and `http.route` is `/pets/{petId}`.
It's a minor adjustment but should help provide clarity for new users.
---------
Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>
2023-03-08 09:12:28 -08:00
489fea52c8
net.peer.name clarification for HTTP client semconv ( #3276 )
...
Fixes #3273
## Changes
Clarifies that if an HTTP client request is explicitly made to an IP
address, e.g. `http://x.x.x.x:8080 `, then
`net.peer.name` SHOULD be the IP address `x.x.x.x`.
2023-03-06 09:33:35 -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
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
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
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
6086a26696
Update exceptions.md ( #3217 )
2023-02-16 05:42:42 -06: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
2165c692f9
Http route should contain application root ( #3164 )
2023-02-06 12:50:01 -08: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
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
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
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
fa6cef115c
Rename grpc metadata attribute names to reflect that they are grpc-specific ( #2981 )
2022-11-22 15:53:34 -08:00
63343b5fbb
Add more semantic convention attributes for Apache RocketMQ ( #2881 )
2022-11-08 16:48:17 +01:00
9f4bd4c0b6
Add gRPC request/response metadata as span attributes ( #2874 )
2022-10-20 13:32:31 -07:00
ace15c86b6
Fix typo in http semantic conventions ( #2896 )
2022-10-20 12:36:13 -07:00
34093ed204
Clarify the HTTP client `http.retry_count` spec ( #2743 )
2022-10-18 10:46:16 -07:00
e2856b8feb
Make messaging context propagation requirements explicit ( #2750 )
2022-09-30 09:05:54 -07:00
3ce713d52b
[Logs] Add semantic conventions for writing exceptions ( #2819 )
2022-09-29 21:38:40 -07:00
c26020299c
Add OpenSearch in the database group ( #2718 )
2022-08-11 20:40:03 +02:00
298c566cf9
Remove alternative attribute sets from HTTP semantic conventions ( #2469 )
2022-07-27 11:31:21 -07:00
216beba6cc
Define net.sock attributes and clarify logical net.peer|host.name attributes ( #2614 )
2022-07-13 10:01:44 -07:00
31a6ecd386
FaaS conventions: make faas.document.time and faas.time attributes recommended ( #2627 )
2022-06-28 16:38:13 +02:00
d27ed53892
cloudevents: relax requirement level for type and version ( #2618 )
2022-06-21 13:29:53 +02:00
9448396526
Add semantic conventions for GraphQL ( #2456 )
...
Add semantic conventions for GraphQL span name and attributes.
Related issues #1670
2022-06-15 15:09:08 -04:00
3f7b7d02f9
Adopt attribute requirement levels in semantic conventions ( #2594 )
2022-06-14 08:02:55 -07:00
35b2b57587
Add semantic convention attributes for capturing the application layer protocol ( #2602 )
2022-06-10 19:09:54 -07:00
22406e7c05
fix typo ( #2595 )
2022-06-01 09:02:17 -07:00
4fae05c1c4
Remove outdated note ( #2540 )
2022-05-24 11:51:58 -07:00
7d2a40e537
Azure FaaS conventions. ( #2502 )
2022-05-13 12:01:20 -07:00
aa58aa8611
Specify how to obtain a Ruby thread's id ( #2508 )
2022-05-05 21:32:47 -07:00
9410cb6131
Fix a typo ( #2523 )
2022-05-04 16:54:00 +02:00
Tristan Sloughter