9976b2abba
Add pull request checks back for links/markdown. ( #5 )
2023-05-11 12:57:26 -04:00
ba20753993
Remove no-changes allowed header from new repository. ( #6 )
2023-05-11 11:46:04 -04:00
554a97dde2
Put hiatus on semantic conventions until they are in the new repository. ( #3489 )
...
As per OTEP:
https://github.com/open-telemetry/oteps/blob/main/text/0227-separate-semantic-conventions.md
2023-05-11 05:59:41 -06:00
f6bee62bfd
Add requirement to use X-Ray propagation for aws-sdk client calls ( #3212 )
2023-05-08 21:22:58 -07:00
614dbefc77
BREAKING: Introduce common `url.*` attributes, and improve use of namespacing under `http.*` ( #3355 )
2023-05-08 19:55:53 -07:00
5b8861e8c5
BREAKING: Replace `net.peer.*`/`net.host.*` with `client.*`/`server.*` (and `source.*`/`destination.*`) ( #3402 )
2023-05-08 16:19:51 -07:00
dcc954abd6
AWS Lambda - remove references to messaging.destination.kind and messaging.source.kind ( #3348 )
2023-03-28 18:14:27 +02:00
efa4181f83
Added AWS S3 semantic conventions ( #3251 )
2023-03-22 08:29:16 -07: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
0d0b9d0a7d
Rename `faas.execution` to `faas.invocation_id` and change units for `faas.max_memory` ( #3209 )
2023-02-20 09:29:24 -06: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
ebcf353c33
Remove rogue bracket ( #3108 )
2023-01-17 09:54:55 -08:00
a7ede6fbfa
Refactor messaging attributes and specify per-message attributes ( #2957 )
2022-12-22 17:04:53 -06: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
d9fbb6f32c
Add Makefile target to auto-generate TOC via markdown-toc ( #2020 )
2021-10-15 15:04:22 +00:00
5bcb639d1d
Lambda instrumentations should check if X-Ray parent context is valid ( #1867 )
2021-08-17 14:28:52 +02:00
25f029b2e2
Rework FaaS semantic conventions. ( #1781 )
2021-07-06 14:34:09 +02:00
795e4ec00f
Remove rpc.jsonrpc.method, clarify rpc.method instead. ( #1748 )
...
* Remove rpc.jsonrpc.method, clarify rpc.method instead.
* Add PR#.
* Clarify client side code.namespace/function.
* Use "ref" instead of "constraint: any_of".
This should be changed back once
https://github.com/open-telemetry/build-tools/issues/33
is resolved & the updated build tools available.
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2021-06-14 16:59:09 -07:00
6c1ab84bb2
Add details for filling resource for AWS Lambda. ( #1610 )
2021-04-15 19:00:34 +02:00
c94d2d1498
AWS SDK common and dynamodb conventions ( #1422 )
...
Co-authored-by: William Armiros <54150514+willarmiros@users.noreply.github.com>
Co-authored-by: Nikita Salnikov-Tarnovski <gnikem@gmail.com>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2021-03-30 18:53:48 +02:00
0f98135322
Add semantic conventions for instrumenting AWS Lambda. ( #1442 )
2021-03-24 22:28:16 +01:00
Josh Suereth