Downgrade otelhttp to v0.37.0

[youngbupark]

Description

There is the bug in otelhttp to use request.RemoteAddr for attributes, which results in high cardinality of the port of remoteaddr. This PR is to use the latest known good release.

open-telemetry/opentelemetry-go-contrib#3765

Issue reference

#5299
#5237

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Adds necessary unit tests for change
• Adds necessary E2E tests for change
• Unit tests passing
• Extended the documentation / Created issue for it

[github-actions]

Test Results

2 514 tests  ±0   2 507 ✔️ ±0   1m 57s ⏱️ +2s
   230 suites ±0          7 💤 ±0 
       1 files   ±0          0 ❌ ±0 

Results for commit 86a9f0b. ± Comparison against base commit 42a6f1b.

This pull request removes 2 and adds 2 tests. Note that renamed tests count towards both.

github.com/project-radius/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/430687f4-6faf-424d-a547-95efbaa122ba
github.com/project-radius/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/430687f4-6faf-424d-a547-95efbaa122ba#01

github.com/project-radius/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/f800eef3-dfa1-4427-a163-e4dbbc7aaecd
github.com/project-radius/radius/pkg/armrpc/frontend/controller ‑ TestValidateEtag_IfMatch/f800eef3-dfa1-4427-a163-e4dbbc7aaecd#01

♻️ This comment has been updated with latest results.

[github-actions]

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

• Your PR branch coverage: 62.1 %
• main branch coverage: 62.1 %
• diff coverage: 0 %

The coverage result does not include the functional test coverage.

[ytimocin]

Should we have an issue to track the work of upgrading back to the latest version once the otelhttp bug is fixed?

[youngbupark]

Should we have an issue to track the work of upgrading back to the latest version once the otelhttp bug is fixed?

There is no benefit to upgrade pkg in the near future since their spec is constantly changing. As I left the comment here, it is better to wait until otelhttp has client side metric features. So I did not create new issue to upgrade it.

[github-actions]

For the detailed report, please go to Checks tab, click Build and Test, and then download unit_test_coverage artifact at the bottom of build page.

• Your PR branch coverage: 62.1 %
• main branch coverage: 62.1 %
• diff coverage: 0 %

The coverage result does not include the functional test coverage.

[youngbupark]

The old version misses status code attribute in http request which is required for our dashboard. So we decide to use the latest version with the workaround. In this case, we need to upgrade pkg as soon as the issue fixes. @vinayada1 will create the issue apart from https://github.com/project-radius/radius/issues/5308#issuecomment-1534984679

Closing this PR.