fix links

open-telemetry · Mar 18, 2021 · a0e2e44 · a0e2e44
1 parent 9305c5d
commit a0e2e44
Show file tree

Hide file tree

Showing 4 changed files with 18 additions and 4 deletions.
diff --git a/specification/glossary.md b/specification/glossary.md
@@ -150,8 +150,10 @@ Synonyms: *Instrumenting Library*.
 ### Tracer Name / Meter Name
 
 This refers to the `name` and (optional) `version` arguments specified when
-creating a new `Tracer` or `Meter` (see [Obtaining a Tracer](trace/api.md#tracerprovider)/[Obtaining a Meter](metrics/api.md#meter-interface)).
-The name/version pair identifies the [Instrumentation Library](#instrumentation-library).
+creating a new `Tracer` or `Meter` (see [Obtaining a
+Tracer](trace/api.md#tracerprovider)/[Obtaining a
+Meter](metrics/api.md#meterprovider)). The name/version pair identifies the
+[Instrumentation Library](#instrumentation-library).
 
 ## Logs
 

diff --git a/specification/metrics/api.md b/specification/metrics/api.md
@@ -206,3 +206,15 @@ A `Measurement` represents a data point reported via the metrics API.
 
 * A value
 * [`Attributes`](../common/common.md#attributes)
+
+## Concurrency
+
+For languages which support concurrent execution the Metrics APIs provide
+specific guarantees and safeties.
+
+**MeterProvider** - all methods are safe to be called concurrently.
+
+**Meter** - all methods are safe to be called concurrently.
+
+**Instrument** - All methods of any Instrument are safe to be called
+concurrently.
diff --git a/specification/metrics/semantic_conventions/openmetrics-guidelines.md b/specification/metrics/semantic_conventions/openmetrics-guidelines.md
@@ -45,7 +45,7 @@ See also [Metric names and labels](https://prometheus.io/docs/concepts/data_mode
 in the Prometheus data model documentation.
 
 OpenMetrics does not allow metric names to begin with a digit. OpenTelemetry's
-[instrument naming requirements](../api.md#instrument-naming-requirements) also
+[instrument naming requirements](../api.md#instrument) also
 require that the first character of a metric instrument is non-numeric.
 
 If a metric event is generated in OpenTelemetry that does not conform to this

diff --git a/specification/resource/sdk.md b/specification/resource/sdk.md
@@ -24,7 +24,7 @@ all `Span`s produced by any `Tracer` from the provider MUST be associated with t
 
 Analogous to distributed tracing, when used with metrics,
 a resource can be associated with a `MeterProvider`.
-When associated with a [`MeterProvider`](../metrics/api.md#meter-interface),
+When associated with a [`MeterProvider`](../metrics/api.md#meterprovider),
 all metrics produced by any `Meter` from the provider will be
 associated with this `Resource`.