opentelemetry-semantic-conventions: Bump to 1.43.0 (#5413)

* opentelemetry-semantic-conventions: Bump to 1.43.0

* Add changelog

---------

Co-authored-by: Lukas Hering <40302054+herin049@users.noreply.github.com>

Author: xrmx

.changelog/5413.changed

@@ -0,0 +1 @@
+`opentelemetry-semantic-conventions`: bump to 1.43.0 

opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/attributes/azure_attributes.py

@@ -46,6 +46,11 @@
 Cosmos DB sub status code.
 """
 
+AZURE_RESOURCE_GROUP_NAME: Final = "azure.resource_group.name"
+"""
+The name of the Azure [resource group](https://learn.microsoft.com/azure/azure-resource-manager/management/manage-resource-groups-portal) the resource belongs to.
+"""
+
 AZURE_RESOURCE_PROVIDER_NAMESPACE: Final = "azure.resource_provider.namespace"
 """
 [Azure Resource Provider Namespace](https://learn.microsoft.com/azure/azure-resource-manager/management/azure-services-resource-providers) as recognized by the client.

opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/attributes/cloud_attributes.py

@@ -7,6 +7,7 @@
 CLOUD_ACCOUNT_ID: Final = "cloud.account.id"
 """
 The cloud account ID the resource is assigned to.
+Note: For Azure, this is the subscription ID.
 """
 
 CLOUD_AVAILABILITY_ZONE: Final = "cloud.availability_zone"

opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/attributes/network_attributes.py

@@ -49,7 +49,7 @@
 
 NETWORK_IO_DIRECTION: Final = "network.io.direction"
 """
-The network IO operation direction.
+The direction of traffic from the perspective of the observing host's physical or virtual network interface. It should not be used to represent the logical direction of a stateful connection or network flow.
 """
 
 NETWORK_LOCAL_ADDRESS: Final = "network.local.address"

opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/attributes/telemetry_attributes.py

@@ -46,6 +46,8 @@ class TelemetrySdkLanguageValues(Enum):
     """Deprecated in favor of stable :py:const:`opentelemetry.semconv.attributes.telemetry_attributes.TelemetrySdkLanguageValues.GO`."""
     JAVA = "java"
     """Deprecated in favor of stable :py:const:`opentelemetry.semconv.attributes.telemetry_attributes.TelemetrySdkLanguageValues.JAVA`."""
+    KOTLIN = "kotlin"
+    """Deprecated in favor of stable :py:const:`opentelemetry.semconv.attributes.telemetry_attributes.TelemetrySdkLanguageValues.KOTLIN`."""
     NODEJS = "nodejs"
     """Deprecated in favor of stable :py:const:`opentelemetry.semconv.attributes.telemetry_attributes.TelemetrySdkLanguageValues.NODEJS`."""
     PHP = "php"

opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/metrics/cicd_metrics.py

@@ -81,7 +81,7 @@ def create_cicd_system_errors(meter: Meter) -> Counter:
 """
 The number of workers on the CI/CD system by state
 Instrument: updowncounter
-Unit: {count}
+Unit: {worker}
 """
 
 
@@ -90,5 +90,5 @@ def create_cicd_worker_count(meter: Meter) -> UpDownCounter:
     return meter.create_up_down_counter(
         name=CICD_WORKER_COUNT,
         description="The number of workers on the CI/CD system by state.",
-        unit="{count}",
+        unit="{worker}",
     )

opentelemetry-semantic-conventions/src/opentelemetry/semconv/_incubating/metrics/otel_metrics.py

@@ -422,6 +422,7 @@ def create_otel_sdk_span_ended_count(meter: Meter) -> Counter:
 The number of created spans with `recording=true` for which the end operation has not been called yet
 Instrument: updowncounter
 Unit: {span}
+Note: Non-recording spans are not counted, hence `otel.span.sampling_result` can only take values `RECORD_ONLY` and `RECORD_AND_SAMPLE`, not `DROP`.
 """
 
 

opentelemetry-semantic-conventions/src/opentelemetry/semconv/attributes/db_attributes.py

@@ -28,8 +28,29 @@
 
 DB_OPERATION_BATCH_SIZE: Final = "db.operation.batch.size"
 """
-The number of queries included in a batch operation.
-Note: Operations are only considered batches when they contain two or more operations, and so `db.operation.batch.size` SHOULD never be `1`.
+The number of database operations included in a batch operation.
+Note: Except for empty batch requests described below, a batch operation contains two
+or more database operations explicitly submitted as separate operations in a single
+client call, protocol message, or database command.
+
+Requests to batch APIs that contain only one operation SHOULD be modeled as single
+operations, not as batch operations.
+
+A database call is not a batch operation solely because one operation accepts
+multiple operands, such as keys, rows, documents, points, or other data elements,
+including Redis [`MGET`](https://redis.io/docs/latest/commands/mget/) with
+multiple keys.
+
+In batch APIs that execute the same parameterized operation with parameter sets,
+each parameter set represents one database operation for determining whether the
+request is a batch operation. Requests with only one parameter set SHOULD be modeled
+as single operations, not as batch operations.
+
+`db.operation.batch.size` SHOULD be set to the number of operations in the batch.
+It SHOULD NOT be set for non-batch operations.
+
+A request to execute a batch operation with no operations SHOULD also be treated
+as a batch operation, and `db.operation.batch.size` SHOULD be set to `0`.
 """
 
 DB_OPERATION_NAME: Final = "db.operation.name"

opentelemetry-semantic-conventions/src/opentelemetry/semconv/attributes/k8s_attributes.py

@@ -82,9 +82,9 @@
 The annotation placed on the DaemonSet, the `<key>` being the annotation name, the value being the annotation value, even if the value is empty.
 Note: Examples:
 
-- A label `replicas` with value `1` SHOULD be recorded
+- An annotation `replicas` with value `1` SHOULD be recorded
   as the `k8s.daemonset.annotation.replicas` attribute with value `"1"`.
-- A label `data` with empty string value SHOULD be recorded as
+- An annotation `data` with empty string value SHOULD be recorded as
   the `k8s.daemonset.annotation.data` attribute with value `""`.
 """
 
@@ -95,7 +95,7 @@
 
 - A label `app` with value `guestbook` SHOULD be recorded
   as the `k8s.daemonset.label.app` attribute with value `"guestbook"`.
-- A label `data` with empty string value SHOULD be recorded as
+- A label `injected` with empty string value SHOULD be recorded as
   the `k8s.daemonset.label.injected` attribute with value `""`.
 """
 
@@ -114,9 +114,9 @@
 The annotation placed on the Deployment, the `<key>` being the annotation name, the value being the annotation value, even if the value is empty.
 Note: Examples:
 
-- A label `replicas` with value `1` SHOULD be recorded
+- An annotation `replicas` with value `1` SHOULD be recorded
   as the `k8s.deployment.annotation.replicas` attribute with value `"1"`.
-- A label `data` with empty string value SHOULD be recorded as
+- An annotation `data` with empty string value SHOULD be recorded as
   the `k8s.deployment.annotation.data` attribute with value `""`.
 """
 
@@ -125,7 +125,7 @@
 The label placed on the Deployment, the `<key>` being the label name, the value being the label value, even if the value is empty.
 Note: Examples:
 
-- A label `replicas` with value `0` SHOULD be recorded
+- A label `app` with value `guestbook` SHOULD be recorded
   as the `k8s.deployment.label.app` attribute with value `"guestbook"`.
 - A label `injected` with empty string value SHOULD be recorded as
   the `k8s.deployment.label.injected` attribute with value `""`.
@@ -146,9 +146,9 @@
 The annotation placed on the Job, the `<key>` being the annotation name, the value being the annotation value, even if the value is empty.
 Note: Examples:
 
-- A label `number` with value `1` SHOULD be recorded
+- An annotation `number` with value `1` SHOULD be recorded
   as the `k8s.job.annotation.number` attribute with value `"1"`.
-- A label `data` with empty string value SHOULD be recorded as
+- An annotation `data` with empty string value SHOULD be recorded as
   the `k8s.job.annotation.data` attribute with value `""`.
 """
 
@@ -159,7 +159,7 @@
 
 - A label `jobtype` with value `ci` SHOULD be recorded
   as the `k8s.job.label.jobtype` attribute with value `"ci"`.
-- A label `data` with empty string value SHOULD be recorded as
+- A label `automated` with empty string value SHOULD be recorded as
   the `k8s.job.label.automated` attribute with value `""`.
 """
 
@@ -178,9 +178,9 @@
 The annotation placed on the Namespace, the `<key>` being the annotation name, the value being the annotation value, even if the value is empty.
 Note: Examples:
 
-- A label `ttl` with value `0` SHOULD be recorded
+- An annotation `ttl` with value `0` SHOULD be recorded
   as the `k8s.namespace.annotation.ttl` attribute with value `"0"`.
-- A label `data` with empty string value SHOULD be recorded as
+- An annotation `data` with empty string value SHOULD be recorded as
   the `k8s.namespace.annotation.data` attribute with value `""`.
 """
 
@@ -302,9 +302,9 @@
 The annotation placed on the ReplicaSet, the `<key>` being the annotation name, the value being the annotation value, even if the value is empty.
 Note: Examples:
 
-- A label `replicas` with value `0` SHOULD be recorded
+- An annotation `replicas` with value `0` SHOULD be recorded
   as the `k8s.replicaset.annotation.replicas` attribute with value `"0"`.
-- A label `data` with empty string value SHOULD be recorded as
+- An annotation `data` with empty string value SHOULD be recorded as
   the `k8s.replicaset.annotation.data` attribute with value `""`.
 """
 
@@ -334,9 +334,9 @@
 The annotation placed on the StatefulSet, the `<key>` being the annotation name, the value being the annotation value, even if the value is empty.
 Note: Examples:
 
-- A label `replicas` with value `1` SHOULD be recorded
+- An annotation `replicas` with value `1` SHOULD be recorded
   as the `k8s.statefulset.annotation.replicas` attribute with value `"1"`.
-- A label `data` with empty string value SHOULD be recorded as
+- An annotation `data` with empty string value SHOULD be recorded as
   the `k8s.statefulset.annotation.data` attribute with value `""`.
 """
 
@@ -345,7 +345,7 @@
 The label placed on the StatefulSet, the `<key>` being the label name, the value being the label value, even if the value is empty.
 Note: Examples:
 
-- A label `replicas` with value `0` SHOULD be recorded
+- A label `app` with value `guestbook` SHOULD be recorded
   as the `k8s.statefulset.label.app` attribute with value `"guestbook"`.
 - A label `injected` with empty string value SHOULD be recorded as
   the `k8s.statefulset.label.injected` attribute with value `""`.

opentelemetry-semantic-conventions/src/opentelemetry/semconv/attributes/telemetry_attributes.py

@@ -49,6 +49,8 @@ class TelemetrySdkLanguageValues(Enum):
     """go."""
     JAVA = "java"
     """java."""
+    KOTLIN = "kotlin"
+    """kotlin."""
     NODEJS = "nodejs"
     """nodejs."""
     PHP = "php"