[pull] main from open-telemetry:main

.chloggen/3919.yaml

@@ -0,0 +1,7 @@
+change_type: enhancement
+component: rpc
+note: >
+  Clarify how to populate `server.address` and `server.port` on RPC server spans.
+  Change requirement level of `server.address` to `opt_in` on `rpc.server.call.duration`
+  metric and to `recommended` on server spans.
+issues: [3784]

.chloggen/3921.yaml

@@ -0,0 +1,4 @@
+change_type: breaking
+component: rpc
+note: Rename `rpc.response.status_code` to `rpc.status_code`.
+issues: [3870]

.chloggen/clarify-log-created-intake.yaml

@@ -0,0 +1,10 @@
+change_type: enhancement
+
+component: otel
+
+note: >
+  Clarify that `otel.sdk.log.created` counts log records at intake on an enabled `Logger`, before per-record filtering.
+
+issues: [3506]
+
+subtext:

.chloggen/error-type-conditionally-required.yaml

@@ -0,0 +1,13 @@
+change_type: enhancement
+
+component: otel
+
+note: >
+  Mark `error.type` as conditionally required on
+  `otel.sdk.processor.{span,log}.processed` and
+  `otel.sdk.exporter.{span,log,metric_data_point}.exported`, matching
+  `otel.sdk.exporter.operation.duration`.
+
+issues: [3954]
+
+subtext:

.chloggen/faas-spans-v2.yaml → .chloggen/fix-multiline-brief-table-cell.yaml

@@ -4,17 +4,17 @@
 # your pull request title with [chore] or use the "Skip Changelog" label.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
+change_type: bug_fix
 
 # The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
-component: faas
+component: docs
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: The general FaaS attributes are now defined on the FaaS spans that use them, so each span documents its full attribute set.
+note: Fix broken Markdown tables when an attribute, metric, or enum-member brief spans multiple lines in YAML.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
 # The values here must be integers.
-issues: [3905]
+issues: [3073]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.

.chloggen/add-k8s-node-inode-metrics.yaml → .chloggen/http-request-response-body.yaml

@@ -4,19 +4,20 @@
 # your pull request title with [chore] or use the "Skip Changelog" label.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: enhancement
+change_type: 'enhancement'
 
 # The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
-component: k8s
+component: 'http'
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "Add `k8s.node.filesystem.inode.count` and `k8s.node.filesystem.inode.free` metrics to track Kubernetes node root filesystem inode capacity and usage."
+note: "Add opt-in `http.request.body.content` and `http.response.body.content` attributes to capture HTTP request and response bodies"
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
 # The values here must be integers.
-issues: [3858]
+issues: [ 857 ]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
-subtext:
+subtext: |
+  These attributes may contain sensitive information.

.chloggen/rc_mem_metrics.yaml → .chloggen/k8s_uptime_rc.yaml

@@ -10,26 +10,19 @@ change_type: enhancement
 component: k8s
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Promote a selection of container and K8s memory metrics to release_candidate
+note: Promote `container.uptime`, `k8s.pod.uptime` and `k8s.node.uptime` metrics to `release_candidate`
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
 # The values here must be integers.
-issues: [3882]
+issues: [3945]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
 subtext: |
   The following metrics are being promoted to release_candidate:
-    - container.memory.usage
-    - container.memory.available
-    - container.memory.rss
-    - container.memory.working_set
-    - k8s.pod.memory.usage
-    - k8s.pod.memory.available
-    - k8s.pod.memory.rss
-    - k8s.pod.memory.working_set
-    - k8s.node.memory.usage
-    - k8s.node.memory.available
-    - k8s.node.memory.rss
-    - k8s.node.memory.working_set
+    - container.uptime
+    - k8s.pod.uptime
+    - k8s.node.uptime
+  Notes referencing the Kubelet stats summary API fields (`ContainerStats.StartTime`,
+  `PodStats.StartTime`, `NodeStats.StartTime`) have been added to each metric.

.chloggen/oracledb-app-context.yaml

@@ -0,0 +1,7 @@
+change_type: enhancement
+component: db
+note: Add application context propagation to Oracle DB via piggybacking
+issues: [3863]
+subtext: |
+  Also recommends driver-provided APIs for updating `V$SESSION.ACTION`
+  instead of issuing SQL or PL/SQL directly.

.chloggen/fix_mem_usage_instr.yaml → .chloggen/restore-sigv2-cloudfront-redaction.yaml

@@ -4,17 +4,17 @@
 # your pull request title with [chore] or use the "Skip Changelog" label.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: breaking
+change_type: bug_fix
 
 # The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
-component: k8s
+component: url
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Change {container, k8s.pod, k8s.node}.memory.usage to updowncounter
+note: Restore `AWSAccessKeyId` and `Signature` to the default list of sensitive query parameter keys.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
 # The values here must be integers.
-issues: [3889]
+issues: [3989]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.

.github/scripts/link-check.sh

@@ -10,6 +10,7 @@ DEPENDENCIES_DOCKERFILE="$ROOT_DIR/dependencies.Dockerfile"
 
 # Parse command line arguments
 LOCAL_LINKS_ONLY=false
+CONFIG_FILE=".github/scripts/lychee-config.toml"
 TARGET=""
 
 while [[ $# -gt 0 ]]; do
@@ -18,6 +19,14 @@ while [[ $# -gt 0 ]]; do
             LOCAL_LINKS_ONLY=true
             shift
             ;;
+        --config)
+            if [[ $# -lt 2 ]]; then
+                echo "Missing value for --config" >&2
+                exit 1
+            fi
+            CONFIG_FILE=$2
+            shift 2
+            ;;
         *)
             # Treat any other arguments as file paths
             TARGET="$TARGET $1"
@@ -44,7 +53,7 @@ fi
 if [[ "$LOCAL_LINKS_ONLY" == "true" ]]; then
     CMD="$CMD --scheme file --include-fragments"
 else
-    CMD="$CMD --config .github/scripts/lychee-config.toml"
+    CMD="$CMD --config $CONFIG_FILE"
 fi
 
 CMD="$CMD $TARGET"

.github/scripts/lychee-spec-links-config.toml

@@ -0,0 +1,12 @@
+include = ["^https://opentelemetry\\.io/docs/specs/otel/"]
+exclude = [".*"]
+
+# Fail when a rendered spec page moves so links can be updated to its canonical URL.
+max_redirects = 0
+include_fragments = true
+
+accept = ["200..=299"]
+max_retries = 6
+retry_wait_time = 5
+timeout = 60
+max_concurrency = 4