open-telemetry
/
semantic-conventions
mirror of https://github.com/open-telemetry/semantic-conventions.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix links still pointing to spec repo main branch (#556)

This commit is contained in:
Joao Grassi 2023-11-24 14:37:17 +01:00 committed by GitHub
parent 0c6d5e1e5a
commit fe200c01bc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/faas/aws-lambda.md
View File

@ -66,7 +66,7 @@ contain an incomplete trace context which indicates X-Ray isn’t enabled. The e
`Context` will be valid and sampled only if AWS X-Ray has been enabled for the Lambda function. A user can `Context` will be valid and sampled only if AWS X-Ray has been enabled for the Lambda function. A user can
disable AWS X-Ray for the function if the X-Ray Span Link is not desired. disable AWS X-Ray for the function if the X-Ray Span Link is not desired.
**Note**: When instrumenting a Java AWS Lambda, instrumentation SHOULD first try to parse an OpenTelemetry `Context` out of the system property `com.amazonaws.xray.traceHeader` using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/context/api-propagators.md) before checking and attempting to parse the environment variable above. **Note**: When instrumenting a Java AWS Lambda, instrumentation SHOULD first try to parse an OpenTelemetry `Context` out of the system property `com.amazonaws.xray.traceHeader` using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/context/api-propagators.md) before checking and attempting to parse the environment variable above.
[Span Link]: https://opentelemetry.io/docs/concepts/signals/traces/#span-links [Span Link]: https://opentelemetry.io/docs/concepts/signals/traces/#span-links

4
docs/messaging/messaging-spans.md
View File

@ -210,7 +210,7 @@ The following operations related to messages are defined for these semantic conv
### Span kind ### Span kind
[Span kinds](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spankind) [Span kinds](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/trace/api.md#spankind)
SHOULD be set according to the following table, based on the operation a span describes. SHOULD be set according to the following table, based on the operation a span describes.
| Operation name | Span kind| | Operation name | Span kind|
@ -221,7 +221,7 @@ SHOULD be set according to the following table, based on the operation a span de
| `deliver` | `CONSUMER` | | `deliver` | `CONSUMER` |
For cases not covered by the table above, the span kind should be set according For cases not covered by the table above, the span kind should be set according
to the [generic specification about span kinds](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spankind), to the [generic specification about span kinds](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/trace/api.md#spankind),
e. g. it should be set to CLIENT for the "Publish" span if its context is not e. g. it should be set to CLIENT for the "Publish" span if its context is not
used as creation context and if the "Publish" span models a synchronous call to used as creation context and if the "Publish" span models a synchronous call to
the intermediary. the intermediary.