Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[chore] Remove resolved TODO about span name prefix #12333

Conversation

jade-guiton-dd
Copy link
Contributor

Description

This PR deletes the TODO comment that sparked #9382. The original intent is a bit unclear, but it is probably addressed by #11769. See tracking issue for discussion and related PRs.

Link to tracking issue

Resolves #9382

@jade-guiton-dd jade-guiton-dd requested a review from a team as a code owner February 10, 2025 17:02
Copy link

codecov bot commented Feb 10, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.39%. Comparing base (44b3eed) to head (b03609d).
Report is 6 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #12333   +/-   ##
=======================================
  Coverage   91.38%   91.39%           
=======================================
  Files         468      468           
  Lines       25610    25624   +14     
=======================================
+ Hits        23404    23418   +14     
  Misses       1790     1790           
  Partials      416      416           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@bogdandrutu
Copy link
Member

The idea is the following, there will be lots of HTTP spans, do we need to distinguish between which are for otlpreceiver vs jaegerreceiver?

@codeboten codeboten added this pull request to the merge queue Feb 10, 2025
Merged via the queue into open-telemetry:main with commit 7f6a9e1 Feb 10, 2025
46 of 59 checks passed
@jade-guiton-dd
Copy link
Contributor Author

@bogdandrutu That would be good, yes. But after the two previous implementation attempts, it seems this is most easily done by specifying a SpanNameFormatter in each of these components. (Worst case scenario: looking at the port and path should be unambiguous, though tedious to look up.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[config/confighttp] Resolve the TODO on confighttp.go related to prefixing operations with component id.
5 participants