-
Notifications
You must be signed in to change notification settings - Fork 389
Make OTEL service names workflow-specific in compiled OTLP workflows #32488
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
Merged
pelikhan
merged 9 commits into
main
from
copilot/fix-workflow-specific-otel-service-names
May 16, 2026
+64
−6
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
de04a21
Initial plan
Copilot a1f0626
fix: make OTEL service name workflow-specific
Copilot 428373d
test: cover OTEL service-name fallback behavior
Copilot 74e04e2
docs: clarify sanitized OTEL service-name format
Copilot 16b5b6e
fix: derive OTEL service name from workflow name
Copilot 3fdd227
test: align OTEL service naming with workflow call name
Copilot fdbf563
fix: prefer workflow ID for OTEL service naming
Copilot 234d1d4
test: add assertion messages for OTEL service-name coverage
Copilot 49ef9ee
Merge branch 'main' into copilot/fix-workflow-specific-otel-service-n…
pelikhan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] The test value
WorkflowID: "Repo Triage/Weekly"doesn't reflect whatWorkflowIDactually looks like at runtime —GetWorkflowIDFromPathalways returns a plain basename without extension (e.g."repo-triage"), never a slash-separated display name.Using a realistic value would make this test a better specification and avoid the false implication that WorkflowID can contain slashes or spaces:
The current value still exercises
SanitizeWorkflowName, but it conflates the WorkflowID and Name concepts in a way that could mislead future readers.