Skip to content

Commit c863656

Browse files
opentelemetrybotopentelemetrybot
authored
[chore] Update spec repo links to v1.42.0 (#1920)
1 parent e708533 commit c863656

35 files changed

+66
-66
lines changed

‎.github/scripts/update-spec-repo-links.sh

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
# ./internal/tools/update-spec-repo-links.sh v1.41.0
66

77
# this version should be kept up-to-date with the spec version that links use
8-
PREVIOUS_SPECIFICATION_VERSION=v1.41.0
8+
PREVIOUS_SPECIFICATION_VERSION=v1.42.0
99

1010
# Set this to the version number you want to KEEP in URLs in the repository.
1111
LATEST_SPECIFICATION_VERSION=$1

‎README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
[![Checks](https://github.com/open-telemetry/semantic-conventions/workflows/Checks/badge.svg?branch=main)](https://github.com/open-telemetry/semantic-conventions/actions?query=workflow%3A%22Checks%22+branch%3Amain)
44
[![GitHub tag (latest SemVer)](https://img.shields.io/github/tag/open-telemetry/semantic-conventions.svg?logo=opentelemetry&&color=f5a800&label=Latest%20release)](https://github.com/open-telemetry/semantic-conventions/releases/latest)
5-
[![Specification Version](https://img.shields.io/badge/OTel_specification_version-v1.41.0-blue?logo=opentelemetry&color=f5a800)](https://github.com/open-telemetry/opentelemetry-specification/releases/tag/v1.41.0)
5+
[![Specification Version](https://img.shields.io/badge/OTel_specification_version-v1.42.0-blue?logo=opentelemetry&color=f5a800)](https://github.com/open-telemetry/opentelemetry-specification/releases/tag/v1.42.0)
66

77
Semantic Conventions define a common set of (semantic) attributes which
88
provide meaning to data when collecting, producing and consuming it.

‎docs/database/cosmosdb.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -318,7 +318,7 @@ This metric is [required][MetricRequired].
318318
It captures the Request Units consumed by each operation in Azure Cosmos DB. Since Request Units serve as a form of throughput control within the Azure Cosmos DB database, monitoring their usage is crucial to avoid throttling.
319319

320320
this metric SHOULD be specified with
321-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
321+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
322322
of `[ 1, 5, 10, 25, 50, 100, 250, 500, 1000]`.
323323

324324
Explaining bucket configuration:

‎docs/database/database-metrics.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ This metric is [required][MetricRequired].
6363
When this metric is reported alongside a database operation span, the metric value SHOULD be the same as the database operation span duration.
6464

6565
This metric SHOULD be specified with
66-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
66+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
6767
of `[ 0.001, 0.005, 0.01, 0.05, 0.1, 0.5, 1, 5, 10 ]`.
6868

6969
<!-- semconv metric.db.client.operation.duration -->
@@ -224,7 +224,7 @@ The following metric instruments describe database query response.
224224
This metric is [recommended][MetricRecommended].
225225

226226
This metric SHOULD be specified with
227-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
227+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
228228
of `[1, 2, 5, 10, 20, 50, 100, 200, 500, 1000, 2000, 5000, 10000]`.
229229

230230
Explaining bucket configuration:

‎docs/database/database-spans.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ with all retries.
5656

5757
## Name
5858

59-
Database spans MUST follow the overall [guidelines for span names](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/trace/api.md#span).
59+
Database spans MUST follow the overall [guidelines for span names](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/trace/api.md#span).
6060

6161
The **span name** SHOULD be `{db.query.summary}` if a summary is available.
6262

‎docs/dns/dns-metrics.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ This document defines semantic conventions to apply when instrumenting DNS queri
2222
This metric is optional.
2323

2424
This metric SHOULD be specified with
25-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
25+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
2626
of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10 ]`.
2727

2828
<!-- semconv metric.dns.lookup.duration -->

‎docs/dotnet/dotnet-aspnetcore-metrics.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ All rate-limiting metrics are reported by the `Microsoft.AspNetCore.RateLimiting
172172
### Metric: `aspnetcore.rate_limiting.request_lease.duration`
173173

174174
this metric SHOULD be specified with
175-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
175+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
176176
of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10 ]`.
177177

178178
<!-- semconv metric.aspnetcore.rate_limiting.request_lease.duration -->
@@ -228,7 +228,7 @@ of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10
228228
### Metric: `aspnetcore.rate_limiting.request.time_in_queue`
229229

230230
this metric SHOULD be specified with
231-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
231+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
232232
of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10 ]`.
233233

234234
<!-- semconv metric.aspnetcore.rate_limiting.request.time_in_queue -->

‎docs/dotnet/dotnet-dns-metrics.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This article defines semantic conventions for DNS metrics emitted by .NET.
2020
### Metric: `dns.lookup.duration`
2121

2222
This metric SHOULD be specified with
23-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
23+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
2424
of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10 ]`.
2525

2626
<!-- Tables in this document are not auto-generated and are intentionally frozen in time. From the .NET perspective this metric and its attributes are stable till the next major version. They are still experimental in the OpenTelemetry. -->

‎docs/dotnet/dotnet-http-metrics.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ Notes:
7777
### Metric: `http.client.connection.duration`
7878

7979
this metric SHOULD be specified with
80-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
80+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
8181
of `[ 0.01, 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10, 30, 60, 120, 300 ]`.
8282

8383
<!-- Tables in this document are not auto-generated and are intentionally frozen in time. From the .NET perspective this metric and its attributes are stable till the next major version. They are still experimental in the OpenTelemetry. -->
@@ -106,7 +106,7 @@ of `[ 0.01, 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10, 30, 60, 120, 300 ]`.
106106
### Metric: `http.client.request.time_in_queue`
107107

108108
this metric SHOULD be specified with
109-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
109+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
110110
of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10 ]`.
111111

112112
<!-- Tables in this document are not auto-generated and are intentionally frozen in time. From the .NET perspective this metric and its attributes are stable till the next major version. They are still experimental in the OpenTelemetry. -->

‎docs/dotnet/dotnet-kestrel-metrics.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ different processes could be listening on TCP port 12345 and UDP port 12345.
9393
## Metric: `kestrel.connection.duration`
9494

9595
this metric SHOULD be specified with
96-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
96+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
9797
of `[ 0.01, 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10, 30, 60, 120, 300 ]`.
9898

9999
<!-- semconv metric.kestrel.connection.duration -->
@@ -474,7 +474,7 @@ different processes could be listening on TCP port 12345 and UDP port 12345.
474474
## Metric: `kestrel.tls_handshake.duration`
475475

476476
this metric SHOULD be specified with
477-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
477+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
478478
of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10 ]`.
479479

480480
<!-- semconv metric.kestrel.tls_handshake.duration -->

‎docs/dotnet/dotnet-signalr-metrics.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This article defines semantic conventions for SignalR metrics emitted by .NET co
1818
## Metric: `signalr.server.connection.duration`
1919

2020
this metric SHOULD be specified with
21-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
21+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
2222
of `[ 0.01, 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10, 30, 60, 120, 300 ]`.
2323

2424
<!-- semconv metric.signalr.server.connection.duration -->

‎docs/exceptions/exceptions-logs.md

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

99
This document defines semantic conventions for recording exceptions on
10-
[logs](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/logs/api.md#emit-a-logrecord)
11-
emitted through the [Logger API](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/logs/api.md#logger).
10+
[logs](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/logs/api.md#emit-a-logrecord)
11+
emitted through the [Logger API](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/logs/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.41.0/specification/logs/data-model.md#log-and-event-record-definition) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/logs/api.md#logger) emit
24+
[LogRecord](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/logs/data-model.md#log-and-event-record-definition) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/logs/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.41.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.42.0/specification/logs/data-model.md#log-and-event-record-definition) and their types.
3737

3838
<!-- semconv log-exception -->
3939
<!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->

‎docs/faas/aws-lambda.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,7 @@ be `<event source> process`. If there are multiple sources in the batch, the nam
161161

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

@@ -174,7 +174,7 @@ See [compatibility](../non-normative/compatibility/aws.md#context-propagation) f
174174
For the SQS message span, the name MUST be `<event source> process`. The parent MUST be the `CONSUMER` span
175175
corresponding to the SQS event. The [message system attributes][] (not message attributes, which are provided by
176176
the user) SHOULD be checked for the key `AWSTraceHeader`. If it is present, an OpenTelemetry `Context` SHOULD be
177-
parsed from the value of the attribute using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/context/api-propagators.md) and
177+
parsed from the value of the attribute using the [AWS X-Ray Propagator](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/context/api-propagators.md) and
178178
added as a link to the span.
179179
See [compatibility](../non-normative/compatibility/aws.md#context-propagation) for more info.
180180

‎docs/faas/faas-metrics.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The following metrics are recorded by the FaaS instance.
4444
This metric is [recommended][MetricRecommended].
4545

4646
This metric SHOULD be specified with
47-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
47+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
4848
of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10 ]`.
4949

5050
<!-- semconv metric.faas.invoke_duration -->
@@ -84,7 +84,7 @@ of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10
8484
This metric is [recommended][MetricRecommended].
8585

8686
This metric SHOULD be specified with
87-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
87+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
8888
of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10 ]`.
8989

9090
<!-- semconv metric.faas.init_duration -->
@@ -304,7 +304,7 @@ This metric is [recommended][MetricRecommended].
304304
This metric is [recommended][MetricRecommended].
305305

306306
This metric SHOULD be specified with
307-
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters)
307+
[`ExplicitBucketBoundaries`](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters)
308308
of `[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10 ]`.
309309

310310
<!-- semconv metric.faas.cpu_usage -->

‎docs/feature-flags/feature-flags-logs.md

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

99
This document defines semantic conventions for recording feature flag evaluations as
10-
a [log record](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/logs/data-model.md#log-and-event-record-definition) emitted through the
11-
[Logger API](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/logs/api.md#emit-a-logrecord).
10+
a [log record](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/logs/data-model.md#log-and-event-record-definition) emitted through the
11+
[Logger API](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/logs/api.md#emit-a-logrecord).
1212
This is useful when a flag is evaluated outside of a transaction context
1313
such as when the application loads or on a timer.
1414

@@ -32,14 +32,14 @@ This can be used to determine the impact a feature has on a request, enabling en
3232
## Recording an Evaluation
3333

3434
Feature flag evaluations SHOULD be recorded as attributes on the
35-
[LogRecord](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/logs/data-model.md#log-and-event-record-definition) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/logs/api.md#logger) emit
35+
[LogRecord](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/logs/data-model.md#log-and-event-record-definition) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/logs/api.md#logger) emit
3636
operations. Evaluations MAY be recorded on "logs" or "events" depending on the
3737
context.
3838

3939
## Evaluation event
4040

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

4444
<!-- semconv event.feature_flag.evaluation -->
4545
<!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->

‎docs/gen-ai/gen-ai-events.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,10 @@ linkTitle: Events
2121

2222
<!-- tocstop -->
2323

24-
GenAI instrumentations MAY capture user inputs sent to the model and responses received from it as [events](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.41.0/specification/logs/data-model.md#events).
24+
GenAI instrumentations MAY capture user inputs sent to the model and responses received from it as [events](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/logs/data-model.md#events).
2525

2626
> Note:
27-
> Events are in-development and not yet available in some languages. Check [spec-compliance matrix](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/spec-compliance-matrix.md#logs) to see the implementation status in corresponding language.
27+
> Events are in-development and not yet available in some languages. Check [spec-compliance matrix](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/spec-compliance-matrix.md#logs) to see the implementation status in corresponding language.
2828
2929
Instrumentations MAY capture inputs and outputs if and only if application has enabled the collection of this data.
3030
This is for three primary reasons:

‎docs/gen-ai/gen-ai-metrics.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -509,4 +509,4 @@ If none of these options apply, the `gen_ai.system` SHOULD be set to `_OTHER`.
509509
[DocumentStatus]: https://opentelemetry.io/docs/specs/otel/document-status
510510
[MetricRequired]: /docs/general/metric-requirement-level.md#required
511511
[MetricRecommended]: /docs/general/metric-requirement-level.md#recommended
512-
[ExplicitBucketBoundaries]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.41.0/specification/metrics/api.md#instrument-advisory-parameters
512+
[ExplicitBucketBoundaries]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.42.0/specification/metrics/api.md#instrument-advisory-parameters

0 commit comments

Comments
 (0)