Merge branch 'main' into baggage-log-record-processor

.github/workflows/Component.BuildTest.yml

@@ -18,7 +18,7 @@ on:
         required: false
         type: string
       os-list:
-        default: '[ "windows-latest", "ubuntu-latest" ]'
+        default: '[ "windows-latest", "ubuntu-22.04" ]'
         required: false
         type: string
       tfm-list:
@@ -46,7 +46,7 @@ jobs:
         os: ${{ fromJSON(inputs.os-list) }}
         version: ${{ fromJSON(inputs.tfm-list) }}
         exclude:
-        - os: ubuntu-latest
+        - os: ubuntu-22.04
           version: net462
         - os: macos-latest
           version: net462
@@ -127,7 +127,7 @@ jobs:
 
     - name: Upload code coverage ${{ inputs.code-cov-prefix }}-${{ inputs.code-cov-name }}
       if: ${{ inputs.run-tests && hashFiles('./TestResults/Cobertura.xml') != '' }}
-      uses: codecov/codecov-action@v4
+      uses: codecov/codecov-action@v5
       continue-on-error: true # Note: Don't fail for upload failures
       env:
         OS: ${{ matrix.os }}

.github/workflows/add-labels.yml

@@ -14,7 +14,7 @@ jobs:
   add-labels-on-issues:
     if: github.event_name == 'issues' && !github.event.issue.pull_request
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     steps:
       - name: check out code
@@ -36,7 +36,7 @@ jobs:
   add-labels-on-pull-requests:
     if: github.event_name == 'pull_request_target'
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     steps:
       - name: check out code

.github/workflows/assign-reviewers.yml

@@ -7,7 +7,7 @@ on:
 
 jobs:
   assign:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     name: Assign Reviewers
     steps:
       - uses: dyladan/component-owners@main

.github/workflows/automation.yml

@@ -18,7 +18,7 @@ on:
 jobs:
   resolve-automation:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     outputs:
       enabled: ${{ steps.evaluate.outputs.enabled }}

.github/workflows/ci-Exporter.OneCollector-Integration.yml

@@ -18,7 +18,7 @@ jobs:
       ${{ github.event_name == 'pull_request_target' &&
       github.event.pull_request.head.repo.full_name != github.repository &&
       'external' || 'internal' }}
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
     - run: echo ✓
 
@@ -28,10 +28,10 @@ jobs:
     strategy:
       fail-fast: false # ensures the entire test matrix is run, even if one permutation fails
       matrix:
-        os: [ windows-latest, ubuntu-latest ]
+        os: [ windows-latest, ubuntu-22.04 ]
         version: [ net462, net8.0 ]
         exclude:
-        - os: ubuntu-latest
+        - os: ubuntu-22.04
           version: net462
 
     runs-on: ${{ matrix.os }}

.github/workflows/ci.yml

@@ -479,7 +479,7 @@ jobs:
     with:
       project-name: Component[OpenTelemetry.Resources.Host]
       code-cov-name: Resources.Host
-      os-list: '[ "windows-latest", "ubuntu-latest", "macos-latest" ]'
+      os-list: '[ "windows-latest", "ubuntu-22.04", "macos-latest" ]'
 
   build-test-resources-operatingsystem:
     needs: detect-changes
@@ -491,7 +491,7 @@ jobs:
     with:
       project-name: Component[OpenTelemetry.Resources.OperatingSystem]
       code-cov-name: Resources.OperatingSystem
-      os-list: '[ "windows-latest", "ubuntu-latest", "macos-latest" ]'
+      os-list: '[ "windows-latest", "ubuntu-22.04", "macos-latest" ]'
 
   build-test-resources-process:
     needs: detect-changes
@@ -628,7 +628,7 @@ jobs:
       verify-aot-compat
     ]
     if: always() && !cancelled()
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
     - run: |
           if ( ${{ contains(needs.*.result, 'failure') }} == true ); then echo 'build failed ✗'; exit 1; else echo 'build complete ✓'; fi

.github/workflows/core-version-update.yml

@@ -14,7 +14,7 @@ jobs:
     secrets: inherit
 
   core-version-update:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     needs: automation
 

.github/workflows/integration.yml

@@ -10,7 +10,7 @@ on:
 jobs:
   redis-integration-test:
     if: inputs.job == 'all' || inputs.job == 'redis-integration-test'
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     strategy:
       fail-fast: false
       matrix:
@@ -23,7 +23,7 @@ jobs:
 
   kafka-integration-test:
     if: inputs.job == 'all' || inputs.job == 'kafka-integration-test'
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     strategy:
       fail-fast: false
       matrix:

.github/workflows/markdownlint.yml

@@ -5,7 +5,7 @@ on:
 
 jobs:
   run-markdownlint:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     steps:
     - name: check out code

.github/workflows/post-release.yml

@@ -16,7 +16,7 @@ jobs:
     secrets: inherit
 
   post-release:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     needs:
     - automation

.github/workflows/prepare-release.yml

@@ -79,7 +79,7 @@ jobs:
     secrets: inherit
 
   prepare-release-pr:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     needs: automation
 
@@ -110,7 +110,7 @@ jobs:
           -gitUserEmail '${{ needs.automation.outputs.email }}'
 
   lock-pr-and-post-notice-to-create-release-tag:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     needs: automation
 
@@ -142,7 +142,7 @@ jobs:
           -botUserName '${{ needs.automation.outputs.username }}'
 
   create-release-tag-unlock-pr-post-notice:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     needs: automation
 
@@ -181,7 +181,7 @@ jobs:
           -gitUserEmail '${{ needs.automation.outputs.email }}'
 
   update-changelog-release-dates-on-prepare-pr-post-notice:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     needs: automation
 
@@ -221,7 +221,7 @@ jobs:
           -gitUserEmail '${{ needs.automation.outputs.email }}'
 
   process-release-request-issue:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     needs: automation
 

.github/workflows/publish-packages.yml

@@ -104,7 +104,7 @@ jobs:
           nuget push src\**\*.nupkg -Source https://api.nuget.org/v3/index.json -ApiKey ${{ secrets.NUGET_TOKEN }} -SymbolApiKey ${{ secrets.NUGET_TOKEN }}
 
   post-build:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     needs:
       - automation

.github/workflows/sanitycheck.yml

@@ -5,7 +5,7 @@ on:
 
 jobs:
   run-misspell:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     steps:
     - name: check out code
@@ -20,7 +20,7 @@ jobs:
       run: ./bin/misspell -error .
 
   run-sanitycheck:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     steps:
     - name: check out code

.github/workflows/stale.yml

@@ -8,7 +8,7 @@ on:
 
 jobs:
   stale:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
       - uses: actions/stale@v9
         with:

.github/workflows/verifyaotcompat.yml

@@ -9,7 +9,7 @@ jobs:
     strategy:
       fail-fast: false # ensures the entire test matrix is run, even if one permutation fails
       matrix:
-        os: [ ubuntu-latest, windows-latest ]
+        os: [ ubuntu-22.04, windows-latest ]
         version: [ net8.0, net9.0 ]
 
     runs-on: ${{ matrix.os }}

.github/workflows/yamllint.yml

@@ -5,7 +5,7 @@ on:
 
 jobs:
   run-yamllint:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
 
     steps:
     - name: check out code

CONTRIBUTING.md

@@ -168,7 +168,7 @@ A PR is considered to be **ready to merge** when:
 
 Any maintainer can merge PRs once they are **ready to merge** however
 maintainers might decide to wait on merging changes until there are more
-approvals and/or dicussion, or based on other factors such as release timing and
+approvals and/or discussion, or based on other factors such as release timing and
 risk to users. For example if a stable release is planned and a new change is
 introduced adding public API(s) or behavioral changes it might be held until the
 next alpha/beta release.

README.md

@@ -94,7 +94,7 @@ repository](https://github.com/open-telemetry/community/blob/main/guides/contrib
 * [Piotr Kiełkowicz](https://github.com/Kielek), Splunk
 
 *Find more about the maintainer role in [community
-repository](h[ttps://github.com/open-telemetry/community/blob/main/community-membership.md#maintainer](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#maintainer)).*
+repository](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#maintainer).*
 
 ### Emeritus
 

src/OpenTelemetry.Exporter.InfluxDB/README.md

@@ -26,7 +26,7 @@ dotnet add package --prerelease OpenTelemetry.Exporter.InfluxDB
 
 ### Step 2: Configure OpenTelemetry MeterProvider
 
-* When using the [OpenTelemetry.Extensions.Hosting](https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Extensions.Hosting/README.md)
+* When using the [OpenTelemetry.Extensions.Hosting](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Extensions.Hosting/README.md)
 package on .NET 6.0+:
 
 ```csharp

src/OpenTelemetry.Extensions.AWS/CHANGELOG.md

@@ -103,4 +103,4 @@ SDK](https://www.nuget.org/packages/OpenTelemetry/).
 The AWSXRay extensions include plugin to generate X-Ray format trace-ids and a
 propagator to propagate the X-Ray trace header to downstream. For more details,
 please refer to the
-[README](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Contrib.Extensions.AWSXRay/README.md)
+[README](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Extensions.AWS/README.md)

src/OpenTelemetry.Instrumentation.AspNet/README.md

@@ -15,17 +15,9 @@ which instruments [ASP.NET](https://docs.microsoft.com/aspnet/overview) and
 collect metrics and traces about incoming web requests.
 
 > [!NOTE]
-> This component is based on the OpenTelemetry semantic conventions for
-[metrics](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/metrics/semantic_conventions)
-and
-[traces](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/semantic_conventions).
-These conventions are
-[Experimental](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/document-status.md),
-and hence, this package is a [pre-release](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/VERSIONING.md#pre-releases).
-Until a [stable
-version](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/telemetry-stability.md)
-is released, there can be breaking changes. You can track the progress from
-[milestones](https://github.com/open-telemetry/opentelemetry-dotnet/milestone/23).
+> This package is a [pre-release](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/VERSIONING.md#pre-releases).
+Until a [stable version](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/telemetry-stability.md)
+is released, there can be breaking changes.
 
 ## Steps to enable OpenTelemetry.Instrumentation.AspNet
 

src/OpenTelemetry.Instrumentation.AspNetCore/README.md

@@ -41,7 +41,7 @@ ASP.NET Core instrumentation must be enabled at application startup. This is
 typically done in the `ConfigureServices` of your `Startup` class. Both examples
 below enables OpenTelemetry by calling `AddOpenTelemetry()` on `IServiceCollection`.
  This extension method requires adding the package
-[`OpenTelemetry.Extensions.Hosting`](../OpenTelemetry.Extensions.Hosting/README.md)
+[`OpenTelemetry.Extensions.Hosting`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Extensions.Hosting/README.md)
 to the application. This ensures instrumentations are disposed when the host
 is shutdown.
 
@@ -51,7 +51,7 @@ The following example demonstrates adding ASP.NET Core instrumentation with the
 extension method `WithTracing()` on `OpenTelemetryBuilder`.
 then extension method `AddAspNetCoreInstrumentation()` on `TracerProviderBuilder`
 to the application. This example also sets up the Console Exporter,
-which requires adding the package [`OpenTelemetry.Exporter.Console`](../OpenTelemetry.Exporter.Console/README.md)
+which requires adding the package [`OpenTelemetry.Exporter.Console`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Exporter.Console/README.md)
 to the application.
 
 ```csharp
@@ -97,7 +97,7 @@ The following example demonstrates adding ASP.NET Core instrumentation with the
 extension method `WithMetrics()` on `OpenTelemetryBuilder`
 then extension method `AddAspNetCoreInstrumentation()` on `MeterProviderBuilder`
 to the application. This example also sets up the Console Exporter,
-which requires adding the package [`OpenTelemetry.Exporter.Console`](../OpenTelemetry.Exporter.Console/README.md)
+which requires adding the package [`OpenTelemetry.Exporter.Console`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Exporter.Console/README.md)
 to the application.
 
 ```csharp
@@ -185,7 +185,7 @@ This instrumentation can be configured to change the default behavior by using
 
 // TODO: This section could be refined.
 When used with
-[`OpenTelemetry.Extensions.Hosting`](../OpenTelemetry.Extensions.Hosting/README.md),
+[`OpenTelemetry.Extensions.Hosting`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Extensions.Hosting/README.md),
 all configurations to `AspNetCoreTraceInstrumentationOptions` can be done in the
 `ConfigureServices`
 method of you applications `Startup` class as shown below.
@@ -270,7 +270,7 @@ services.AddOpenTelemetry()
         }));
 ```
 
-[Processor](../../docs/trace/extending-the-sdk/README.md#processor),
+[Processor](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/docs/trace/extending-the-sdk/README.md#processor),
 is the general extensibility point to add additional properties to any activity.
 The `Enrich` option is specific to this instrumentation, and is provided to
 get access to `HttpRequest` and `HttpResponse`.
@@ -365,8 +365,8 @@ This component uses an
 [EventSource](https://docs.microsoft.com/dotnet/api/system.diagnostics.tracing.eventsource)
 with the name "OpenTelemetry-Instrumentation-AspNetCore" for its internal
 logging. Please refer to [SDK
-troubleshooting](../OpenTelemetry/README.md#troubleshooting) for instructions on
-seeing these internal logs.
+troubleshooting](https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry/README.md#troubleshooting)
+for instructions on seeing these internal logs.
 
 ## References
 

src/OpenTelemetry.Instrumentation.Cassandra/README.md

@@ -63,7 +63,7 @@ public class Program
 
 For an ASP.NET Core application, adding instrumentation is typically done in
 the `ConfigureServices` of your `Startup` class. Refer to documentation for
-[OpenTelemetry.Instrumentation.AspNetCore](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Instrumentation.AspNetCore/README.md).
+[OpenTelemetry.Instrumentation.AspNetCore](../OpenTelemetry.Instrumentation.AspNetCore/README.md).
 
 For an ASP.NET application, adding instrumentation is typically done in the
 `Global.asax.cs`. Refer to documentation for [OpenTelemetry.Instrumentation.AspNet](../OpenTelemetry.Instrumentation.AspNet/README.md).
@@ -101,6 +101,6 @@ var cluster = new Builder()
 
 * [OpenTelemetry Project](https://opentelemetry.io/)
 
-* [OpenTelemetry semantic conventions for database calls](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/database.md)
+* [OpenTelemetry semantic conventions for Cassandra](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/cassandra.md)
 
 * [Cassandra C# Driver](https://github.com/datastax/csharp-driver)