Opentelemetry span name (#10123) (master up-port)

[ashishb-solo]

Description

up-port of #10123 to master

API changes

See linked pull request

Code changes

See linked pull request

Docs changes

See linked pull request

Context

Interesting decisions

Testing steps

Notes for reviewers

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

BOT NOTES:
resolves #9848

[solo-changelog-bot]

Issues linked to changelog:
#9848

[github-actions]

Visit the preview URL for this PR (updated for commit 30a4fb9):

https://gloo-edge--pr10297-opentelemetry-span-n-2gqzpjcx.web.app

_{(expires Mon, 18 Nov 2024 20:39:01 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 77c2b86e287749579b7ff9cadb81e099042ef677}

[sam-heilbron]

Looks like there are some unintentional codegen changes (proto versions). Fixing this should resolve the static code analysis job.

It looks like 2 e2e test suites failed. Can you investigate, and if we need to open flake issues or record a failure on an existing one, do that?

I see that build-bot did not start on this PR. Can you investigate that?

[ashishb-solo]

Looks like there are some unintentional codegen changes (proto versions). Fixing this should resolve the static code analysis job.

Fixed by re-running make install-go-tools

It looks like 2 e2e test suites failed. Can you investigate, and if we need to open flake issues or record a failure on an existing one, do that?

Almost definitely flakes. Will update the relevant issues and/or create them.

I see that build-bot did not start on this PR. Can you investigate that?

I'm going to guess that this is a one-off thing. Do you think we're in the clear on this, or if not have any suggestions on how to investigate this further?