test(golang): add go-restful OTel semantics weblog

[marcotc]

Motivation

APMAPI-2047 extends the OpenTelemetry HTTP semantics RFC system-test coverage to a real go-restful v3 server integration.

This PR builds on #7573, which owns the shared OpenTelemetry HTTP test expectation changes.

Changes

• Add a minimal go-restful-v3 Go weblog with framework-native route matching and traced net/http downstream calls.
• Add shared router-neutral endpoint behavior for OpenTelemetry HTTP semantics weblogs.
• Schedule the weblog only for the four existing OpenTelemetry HTTP semantics scenarios.
• Keep the legacy scenario-matrix parity check aligned with the restricted weblog variant.

Validation

The weblog builds and passes all forced semantic test classes against dd-trace-go commit 3f75582cb90f232ddcace4ebd2fc7a2296320851. ./format.sh, scenario-selection validation, and relevant TEST_THE_TEST checks also pass.

Stack

• Base: fix(otel): correct trace metric status and endpoint coverage #7573
• This PR: go-restful v3 weblog
• Next: test(golang): add Gorilla OTel semantics weblog #7584, Gorilla mux weblog

Gotchas

The Go manifest remains unchanged because the go-restful semantics implementation is not merged into dd-trace-go main. The semantic classes therefore remain marked missing_feature until the implementation merges and its release version can be recorded.

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• Anything but tests/ or manifests/ is modified ? I have the approval from R&P team
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added, removed or renamed?
  • Get a review from R&P team

[github-actions]

CODEOWNERS have been resolved as:

utils/build/docker/golang/app/_shared/otel_semantics/handlers.go        @DataDog/system-tests-reviewers
utils/build/docker/golang/app/go-restful-v3/main.go                     @DataDog/system-tests-reviewers
utils/build/docker/golang/go-restful-v3.Dockerfile                      @DataDog/system-tests-reviewers
docs/execute/build.md                                                   @DataDog/system-tests-core
tests/test_the_test/test_ci_orchestrator.py                             @DataDog/system-tests-core
utils/build/docker/golang/app/go.mod                                    @DataDog/system-tests-reviewers
utils/build/docker/golang/app/go.sum                                    @DataDog/system-tests-reviewers
utils/build/docker/golang/weblog_metadata.yml                           @DataDog/system-tests-reviewers

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5aef48d268

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[datadog-official]

 

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 2 Pipeline jobs failed

DataDog/system-tests | Ubuntu_24_amd64.HOS: [test-app-dotnet]

View more details · View in GitLab

Testing the test | all-jobs-are-green

View more details · View in GitHub Actions

Job did not run due to failed CI checks or statuses.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🔄 Datadog auto-retried 2 jobs - 1 passed on retry

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0c713fe | Docs | View more details | Give us feedback!}

[link04]

LGTM nothing I could find, not sure if anyone from Go can take a look.