Skip to content

Commit 18400cf

Browse files
jsuerethjsuereth
authored
Bump to latest version of the specification. (open-telemetry#185)
1 parent c6efa4b commit 18400cf

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

80 files changed

+118
-118
lines changed

‎README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -41,4 +41,4 @@ Maintainers ([@open-telemetry/specs-semconv-maintainers](https://github.com/orgs
4141

4242
*Find more about the maintainer role in [community repository](https://github.com/open-telemetry/community/blob/master/community-membership.md#maintainer).*
4343

44-
[SpecificationVersion]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0
44+
[SpecificationVersion]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0

‎docs/cloud-providers/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -15,4 +15,4 @@ Semantic conventions exist for the following cloud provider SDKs:
1515

1616
* [AWS SDK](aws-sdk.md): Semantic Conventions for the *AWS SDK*.
1717

18-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
18+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/cloud-providers/aws-sdk.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -43,4 +43,4 @@ The following Semantic Conventions extend the general AWS SDK attributes for spe
4343
* [AWS DynamoDB](/docs/database/dynamodb.md): Semantic Conventions for *AWS DynamoDB*.
4444
* [AWS S3](/docs/object-stores/s3.md): Semantic Conventions for *AWS S3*.
4545

46-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
46+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/cloudevents/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -15,4 +15,4 @@ Semantic conventions for CloudEvents are defined for the following signals:
1515

1616
* [CloudEvents Spans](cloudevents-spans.md): Semantic Conventions for modeling CloudEvents as *spans*.
1717

18-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
18+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/cloudevents/cloudevents-spans.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -207,4 +207,4 @@ The following attributes are applicable to creation and processing Spans.
207207
| `cloudevents.event_subject` | string | The [subject](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md#subject) of the event in the context of the event producer (identified by source). | `mynewfile.jpg` | Recommended |
208208
<!-- endsemconv -->
209209

210-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
210+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -31,4 +31,4 @@ Technology specific semantic conventions are defined for the following databases
3131
* [Redis](redis.md): Semantic Conventions for *Redis*.
3232
* [SQL](sql.md): Semantic Conventions for *SQL* databases.
3333

34-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
34+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/cassandra.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -47,4 +47,4 @@ described on this page.
4747
| `local_serial` | local_serial |
4848
<!-- endsemconv -->
4949

50-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
50+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/cosmosdb.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -90,4 +90,4 @@ In addition to Cosmos DB attributes, all spans include
9090
| `db.cosmosdb.sub_status_code` | `0` |
9191
| `db.cosmosdb.request_charge` | `7.43` |
9292

93-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
93+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/couchdb.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,4 +22,4 @@ described on this page.
2222
**[1]:** In **CouchDB**, `db.operation` should be set to the HTTP method + the target REST route according to the API reference documentation. For example, when retrieving a document, `db.operation` would be set to (literally, i.e., without replacing the placeholders with concrete values): [`GET /{db}/{docid}`](http://docs.couchdb.org/en/stable/api/document/common.html#get--db-docid).
2323
<!-- endsemconv -->
2424

25-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
25+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/database-metrics.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -60,4 +60,4 @@ Below is a table of the attributes that MUST be included on all connection pool
6060
|-------------|--------|------------------------------------------------------------------------------|----------------|-------------------|
6161
| `pool.name` | string | The name of the connection pool; unique within the instrumented application. In case the connection pool implementation does not provide a name, then the [db.connection_string](/docs/database/database-spans.md#connection-level-attributes) should be used. | `myDataSource` | Required |
6262

63-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
63+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/database-spans.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -190,4 +190,4 @@ More specific Semantic Conventions are defined for the following database techno
190190
* [Redis](redis.md): Semantic Conventions for *Redis*.
191191
* [SQL](sql.md): Semantic Conventions for *SQL* databases.
192192

193-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
193+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/dynamodb.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -170,4 +170,4 @@ These attributes are filled in for all DynamoDB request types.
170170
| `aws.dynamodb.table_names` | string[] | A single-element array with the value of the TableName request parameter. | `[Users]` | Recommended |
171171
<!-- endsemconv -->
172172

173-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
173+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/elasticsearch.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -83,4 +83,4 @@ Tracing instrumentations that do so, MUST also set `http.request.method_original
8383
| `url.full` | `"https://elasticsearch.mydomain.com:9200/my-index-000001/_search?from=40&size=20"` |
8484
| `db.elasticsearch.path_parts.index` | `"my-index-000001"` |
8585

86-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
86+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/graphql.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -32,4 +32,4 @@ MAY be used as span name.
3232
| `subscription` | GraphQL subscription |
3333
<!-- endsemconv -->
3434

35-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
35+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/hbase.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,4 +22,4 @@ described on this page.
2222
**[1]:** For HBase the `db.name` should be set to the HBase namespace.
2323
<!-- endsemconv -->
2424

25-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
25+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/mongodb.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -37,4 +37,4 @@ described on this page.
3737
| `db.operation` | `"findAndModify"` |
3838
| `db.mongodb.collection` | `"products"` |
3939

40-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
40+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/mssql.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -23,4 +23,4 @@ described on this page.
2323
**[1]:** If setting a `db.mssql.instance_name`, `server.port` is no longer required (but still recommended if non-standard).
2424
<!-- endsemconv -->
2525

26-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
26+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/redis.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -43,4 +43,4 @@ Furthermore, `db.name` is not specified as there is no database name in Redis an
4343
| `db.operation` | not set |
4444
| `db.redis.database_index` | `15` |
4545

46-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
46+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/database/sql.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -39,4 +39,4 @@ This is an example of attributes for a MySQL database span:
3939
| `db.operation` | `"SELECT"` |
4040
| `db.sql.table` | `"orders"` |
4141

42-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
42+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/exceptions/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -16,4 +16,4 @@ Semantic conventions for Exceptions are defined for the following signals:
1616
* [Exceptions on spans](exceptions-spans.md): Semantic Conventions for Exceptions associated with *spans*.
1717
* [Exceptions in logs](exceptions-logs.md): Semantic Conventions for Exceptions recorded in *logs*.
1818

19-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
19+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/exceptions/exceptions-logs.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ linkTitle: Logs
77
**Status**: [Experimental][DocumentStatus]
88

99
This document defines semantic conventions for recording exceptions on
10-
[logs](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/logs/bridge-api.md#emit-a-logrecord) and [events](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/logs/event-api.md#emit-event)
11-
emitted through the [Logger API](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/logs/bridge-api.md#logger).
10+
[logs](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/logs/bridge-api.md#emit-a-logrecord) and [events](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/logs/event-api.md#emit-event)
11+
emitted through the [Logger API](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/logs/bridge-api.md#logger).
1212

1313
<!-- toc -->
1414

@@ -21,7 +21,7 @@ emitted through the [Logger API](https://github.com/open-telemetry/opentelemetry
2121
## Recording an Exception
2222

2323
Exceptions SHOULD be recorded as attributes on the
24-
[LogRecord](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/logs/data-model.md#log-and-event-record-definition) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/logs/bridge-api.md#logger) emit
24+
[LogRecord](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/logs/data-model.md#log-and-event-record-definition) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/logs/bridge-api.md#logger) emit
2525
operations. Exceptions MAY be recorded on "logs" or "events" depending on the
2626
context.
2727

@@ -33,7 +33,7 @@ the language runtime.
3333
## Attributes
3434

3535
The table below indicates which attributes should be added to the
36-
[LogRecord](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/logs/data-model.md#log-and-event-record-definition) and their types.
36+
[LogRecord](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/logs/data-model.md#log-and-event-record-definition) and their types.
3737

3838
<!-- semconv log-exception -->
3939
| Attribute | Type | Description | Examples | Requirement Level |
@@ -53,4 +53,4 @@ The table below indicates which attributes should be added to the
5353
Same as [Trace Semantic Conventions for Exceptions - Stacktrace
5454
Representation](exceptions-spans.md#stacktrace-representation).
5555

56-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
56+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/exceptions/exceptions-spans.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ An exception SHOULD be recorded as an `Event` on the span during which it occurr
2323
The name of the event MUST be `"exception"`.
2424

2525
A typical template for an auto-instrumentation implementing this semantic convention
26-
using an [API-provided `recordException` method](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/trace/api.md#record-exception)
26+
using an [API-provided `recordException` method](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/trace/api.md#record-exception)
2727
could look like this (pseudo-Java):
2828

2929
```java
@@ -109,4 +109,4 @@ grained information from a stacktrace, if necessary.
109109
[telemetry-sdk-resource]: ../resource/README.md#telemetry-sdk
110110
[erlang-stacktrace]: https://www.erlang.org/doc/man/erl_error.html#format_exception-3
111111
[elixir-stacktrace]: https://hexdocs.pm/elixir/1.14.3/Exception.html#format/3
112-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
112+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/faas/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,4 +20,4 @@ Technology specific semantic conventions are defined for the following FaaS serv
2020

2121
* [AWS Lambda](aws-lambda.md): Semantic Conventions for *AWS Lambda*.
2222

23-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
23+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/faas/aws-lambda.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -57,9 +57,9 @@ and the [cloud resource conventions][cloud]. The following AWS Lambda-specific a
5757
### AWS X-Ray Environment Span Link
5858

5959
If the `_X_AMZN_TRACE_ID` environment variable is set, instrumentation SHOULD try to parse an
60-
OpenTelemetry `Context` out of it using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/context/api-propagators.md). If the
61-
resulting `Context` is [valid](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/trace/api.md#isvalid) then a [Span Link][] SHOULD be added to the new Span's
62-
[start options](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/trace/api.md#specifying-links) with an associated attribute of `source=x-ray-env` to
60+
OpenTelemetry `Context` out of it using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/context/api-propagators.md). If the
61+
resulting `Context` is [valid](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/trace/api.md#isvalid) then a [Span Link][] SHOULD be added to the new Span's
62+
[start options](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/trace/api.md#specifying-links) with an associated attribute of `source=x-ray-env` to
6363
indicate the source of the linked span.
6464
Instrumentation MUST check if the context is valid before using it because the `_X_AMZN_TRACE_ID` environment variable can
6565
contain an incomplete trace context which indicates X-Ray isn’t enabled. The environment variable will be set and the
@@ -109,7 +109,7 @@ be `<event source> process`. If there are multiple sources in the batch, the nam
109109

110110
For every message in the event, the [message system attributes][] (not message attributes, which are provided by
111111
the user) SHOULD be checked for the key `AWSTraceHeader`. If it is present, an OpenTelemetry `Context` SHOULD be
112-
parsed from the value of the attribute using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/context/api-propagators.md) and
112+
parsed from the value of the attribute using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/context/api-propagators.md) and
113113
added as a link to the span. This means the span may have as many links as messages in the batch.
114114
See [compatibility](../../supplementary-guidelines/compatibility/aws.md#context-propagation) for more info.
115115

@@ -123,7 +123,7 @@ See [compatibility](../../supplementary-guidelines/compatibility/aws.md#context-
123123
For the SQS message span, the name MUST be `<event source> process`. The parent MUST be the `CONSUMER` span
124124
corresponding to the SQS event. The [message system attributes][] (not message attributes, which are provided by
125125
the user) SHOULD be checked for the key `AWSTraceHeader`. If it is present, an OpenTelemetry `Context` SHOULD be
126-
parsed from the value of the attribute using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.21.0/specification/context/api-propagators.md) and
126+
parsed from the value of the attribute using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/context/api-propagators.md) and
127127
added as a link to the span.
128128
See [compatibility](../../supplementary-guidelines/compatibility/aws.md#context-propagation) for more info.
129129

@@ -250,4 +250,4 @@ because it is not available until function invocation.
250250

251251
[environment variables]: https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#configuration-envvars-runtime
252252

253-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
253+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/faas/faas-metrics.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -82,4 +82,4 @@ FaaS providers. This list is not exhaustive.
8282
* [Google CloudFunctions Metrics](https://cloud.google.com/monitoring/api/metrics_gcp#gcp-cloudfunctions)
8383
* [OpenFaas Metrics](https://docs.openfaas.com/architecture/metrics/)
8484

85-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
85+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/faas/faas-spans.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -261,4 +261,4 @@ This example shows the FaaS attributes for a (non-FaaS) process hosted on Google
261261
| Resource | `faas.instance` | n/a | `"my-lambda-function:instance-0001"` |
262262
| Resource | `cloud.resource_id` | n/a | `"arn:aws:lambda:us-west-2:123456789012:function:my-lambda-function"` |
263263

264-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
264+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

‎docs/feature-flags/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,4 +17,4 @@ Semantic conventions for feature flags are defined for the following signals:
1717
* [Feature Flags in Spans](feature-flags-spans.md): Semantic Conventions for recording feature flags in *spans*.
1818
* [Feature Flags in Logs](feature-flags-logs.md): Semantic Conventions for recording feature flags in *logs*.
1919

20-
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
20+
[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/document-status.md

0 commit comments

Comments
 (0)