Add k8s.node in semantic conventions

open-telemetry · Jan 14, 2021 · bdac833 · bdac833
1 parent d4d2020
commit bdac833
Showing 1 changed file with 13 additions and 0 deletions.
diff --git a/specification/resource/semantic_conventions/k8s.md b/specification/resource/semantic_conventions/k8s.md
@@ -25,6 +25,19 @@ Kubernetes object, but "name" is usually more user friendly so can be also set.
 | `k8s.cluster.name` | string | The name of the cluster. | `opentelemetry-cluster` | No |
 <!-- endsemconv -->
 
+## Node
+
+**type:** `k8s.node`
+
+**Description:** A Kubernetes Node.
+
+<!-- semconv k8s.node -->
+| Attribute  | Type | Description  | Example  | Required |
+|---|---|---|---|---|
+| `k8s.node.name` | string | The name of the node. | `opentelemetry-node` | No |
+| `k8s.node.ip` | string | The address of the node (dotted decimal for IPv4 or [RFC5952](https://tools.ietf.org/html/rfc5952) for IPv6. | `127.0.0.1` | No |
+<!-- endsemconv -->
+
 ## Namespace
 
 Namespaces provide a scope for names. Names of objects need to be unique within