From ee634c0fb39085e5bb5826aa081d1c1f958123a7 Mon Sep 17 00:00:00 2001 From: David Ashpole Date: Tue, 16 Aug 2022 14:40:04 +0000 Subject: [PATCH] regenerate tables --- specification/scope/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/scope/README.md b/specification/scope/README.md index 1f3293d84a6..8e9d3226a05 100644 --- a/specification/scope/README.md +++ b/specification/scope/README.md @@ -7,5 +7,5 @@ This document defines standard attributes for the [instrumentation scope](../glo | Attribute | Type | Description | Examples | Requirement Level | |---|---|---|---|---| -| `scope.short_name` | string | The short name for the instrumentation scope, which should generally be less than 15 characters, and generally consist of a single word. It is not required to be globally unique, but should be unique enough to make it very unlikely to collide with other short names. An example use is as the [namespace](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#metric-naming-and-namespaces) (prefix) for OpenMetrics metric names. | `mylibrary`; `otelhttp` | Recommended | +| `short_name` | string | The short name for the instrumentation scope, which should generally be less than 15 characters, and generally consist of a single word. It is not required to be globally unique, but should be unique enough to make it very unlikely to collide with other short names. An example use is as the [namespace](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#metric-naming-and-namespaces) (prefix) for OpenMetrics metric names. It is recommended for the short_name to be related to the name of the scope. | `mylibrary`; `otelmacaron` | Recommended |