Clarify name used by container runtime

open-telemetry · Oct 1, 2021 · bc185e9 · bc185e9
1 parent 0b24e0e
commit bc185e9
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/semantic_conventions/resource/k8s.yaml b/semantic_conventions/resource/k8s.yaml
@@ -62,8 +62,8 @@ groups:
         type: string
         brief: >
           The name of the Container from Pod specification, must be unique
-          within a Pod. Container runtime usually uses different name unique
-          within a Cluster (`container.name`).
+          within a Pod. Container runtime usually uses different globally unique
+          name (`container.name`).
         examples: ['redis']
 
   - id: k8s.replicaset

diff --git a/specification/resource/semantic_conventions/k8s.md b/specification/resource/semantic_conventions/k8s.md
@@ -87,7 +87,7 @@ to a running container.
 <!-- semconv k8s.container -->
 | Attribute  | Type | Description  | Examples  | Required |
 |---|---|---|---|---|
-| `k8s.container.name` | string | The name of the Container from Pod specification, must be unique within a Pod. Container runtime usually uses different name unique within a Cluster (`container.name`). | `redis` | No |
+| `k8s.container.name` | string | The name of the Container from Pod specification, must be unique within a Pod. Container runtime usually uses different globally unique name (`container.name`). | `redis` | No |
 <!-- endsemconv -->
 
 ## ReplicaSet