Merge branch 'main' into clarify_target_info

.github/ISSUE_TEMPLATE/project.md

@@ -0,0 +1,51 @@
+---
+name: Project Tracking Issue
+about: Proposals for large-scale specification work which requires a group effort.
+labels: spec:project-tracking
+---
+
+### Description
+
+Describe the goals, objectives, and requirements for the project. This include the motivations for starting the project now, as opposed to later.
+
+### Project Board
+
+Once approved by TC, a project should be managed using a GitHub project board. This project board should be pre-populated with issues that cover all known deliverables, organized by timeline milestones.
+
+A [Technical Committee](https://github.com/open-telemetry/community/blob/main/community-members.md#technical-committee) (TC) member associated with the project can create the board, along with a new project-specific GitHub label to automatically associate issues and PRs with the project. The project lead and all other relevant project members should have edit access to the board.
+
+Once created, please link to the project board here.
+
+### Deliverables
+
+A description of what this project is planning to deliver, or is in the process of delivering. This includes all OTEPs and their associated prototypes.
+
+In general, OTEPs are not accepted unless they come with working prototypes available to review in at least two languages. Please discuss these requirements with a TC member before submitting an OTEP.
+
+### Staffing / Help Wanted
+
+Who is currently planning to work on the project? If a project requires specialized domain expertise, please list it here. If a project is missing a critical mass of people in order to begin work, please clarify.
+
+#### Required staffing
+
+Projects cannot be started until they the following participants have been identified:
+* Every project needs a project lead, who is willing to bottom line the project and address any issues which are not handled by other project members.
+* At least two sponsoring TC members. TC sponsors are dedicated to attending meetings, reviewing proposals, and in general being aware of the state of the project and it's technical details. TC sponsors guide the project through the spec process, keep the tracking issue up to date, and help to ensure that relevant community members provide input at the appropriate times.
+* Engineers willing to write prototypes in at least two languages (if relevant to project). Languages should be fairly different from each other (for example: Java and Python).
+* Maintainers or approvers from those languages committed to reviewing the prototypes.
+
+### Meeting Times
+
+Once a project is started, the working group should meet regularly for discussion. These meeting times should be posted on the OpenTelemetry public calendar.
+
+### Timeline
+
+What is the expected timeline the project will aim to adhere to, and what resources and deliverables will be needed for each portion of the timeline? If the project has not been started, please describe this timeline in relative terms (one month in, two weeks later, etc). If a project has started, please include actual dates.
+
+### Labels
+
+The tracking issue should be properly labeled to indicate what parts of the specification it is focused on.
+
+### Linked Issues and PRs
+
+All PRs, Issues, and OTEPs related to the project should link back to the tracking issue, so that they can be easily found. 

CHANGELOG.md

@@ -59,11 +59,16 @@ release.
   ([#2650](https://github.com/open-telemetry/opentelemetry-specification/pull/2650)).
 - Improve the definition of `state` attribute for metric `system.network.connections`
   ([#2663](https://github.com/open-telemetry/opentelemetry-specification/pull/2663))
+- Add `process.parent_pid` attribute for use in reporting parent process id (PID)
+  ([#2691](https://github.com/open-telemetry/opentelemetry-specification/pull/2691)).
 
 ### Compatibility
 
 ### OpenTelemetry Protocol
 
+- Add support for partial success in an OTLP export response
+  ([#2696](https://github.com/open-telemetry/opentelemetry-specification/pull/2696)).
+
 ### SDK Configuration
 
 - Mark `OTEL_METRIC_EXPORT_INTERVAL`, `OTEL_METRIC_EXPORT_TIMEOUT`

internal/tools/schema_check.sh

@@ -6,7 +6,7 @@
 
 set -e
 
-BUILD_TOOL_SCHEMAS_VERSION=0.12.1
+BUILD_TOOL_SCHEMAS_VERSION=0.13.0
 
 # List of vesions that do not require or have a schema.
 declare -a skip_versions=("1.0.0" "1.0.1" "1.1.0" "1.2.0" "1.3.0" "1.6.0")

schemas/1.13.0

@@ -0,0 +1,105 @@
+file_format: 1.1.0
+schema_url: https://opentelemetry.io/schemas/1.13.0
+versions:
+  1.13.0:
+    metrics:
+      changes:
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: system.paging.operations
+            by_attribute: direction
+            metrics_from_attributes:
+                system.paging.operations.in: in
+                system.paging.operations.out: out
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: system.disk.io
+            by_attribute: direction
+            metrics_from_attributes:
+                system.disk.io.read: read
+                system.disk.io.write: write
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: system.disk.operations
+            by_attribute: direction
+            metrics_from_attributes:
+                system.disk.operations.read: read
+                system.disk.operations.write: write
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: system.disk.operation_time
+            by_attribute: direction
+            metrics_from_attributes:
+                system.disk.operation_time.read: read
+                system.disk.operation_time.write: write
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: system.disk.merged
+            by_attribute: direction
+            metrics_from_attributes:
+                system.disk.merged.read: read
+                system.disk.merged.write: write
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: system.network.dropped
+            by_attribute: direction
+            metrics_from_attributes:
+                system.network.dropped.receive: receive
+                system.network.dropped.transmit: transmit
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: system.network.packets
+            by_attribute: direction
+            metrics_from_attributes:
+                system.network.packets.receive: receive
+                system.network.packets.transmit: transmit
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: system.network.errors
+            by_attribute: direction
+            metrics_from_attributes:
+                system.network.errors.receive: receive
+                system.network.errors.transmit: transmit
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: system.network.io
+            by_attribute: direction
+            metrics_from_attributes:
+                system.network.io.receive: receive
+                system.network.io.transmit: transmit
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: process.disk.io
+            by_attribute: direction
+            metrics_from_attributes:
+                process.disk.io.read: read
+                process.disk.io.write: write
+        # https://github.com/open-telemetry/opentelemetry-specification/pull/2617
+        - split:
+            apply_to_metric: process.network.io
+            by_attribute: direction
+            metrics_from_attributes:
+                process.network.io.receive: receive
+                process.network.io.transmit: transmit
+
+  1.12.0:
+    spans:
+      changes:
+        - rename_attributes:
+            attribute_map:
+              net.peer.ip: net.sock.peer.addr
+              net.host.ip: net.sock.host.addr
+  1.11.0:
+  1.10.0:
+  1.9.0:
+  1.8.0:
+    spans:
+      changes:
+        - rename_attributes:
+            attribute_map:
+              db.cassandra.keyspace: db.name
+              db.hbase.namespace: db.name
+  1.7.0:
+  1.6.1:
+  1.5.0:
+  1.4.0:

semantic_conventions/resource/process.yaml

@@ -10,6 +10,11 @@ groups:
         brief: >
           Process identifier (PID).
         examples: [1234]
+      - id: parent_pid
+        type: int
+        brief: >
+          Parent Process identifier (PID).
+        examples: [111]
       - id: executable.name
         type: string
         requirement_level: