-
Notifications
You must be signed in to change notification settings - Fork 2.9k
[processor/transform] Introduce optional metric name suffix setup for convert summary and extract histogram functions #37238
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
evan-bradley
merged 26 commits into
open-telemetry:main
from
odubajDT:transform-name-suffix
Jun 23, 2025
Merged
Changes from 4 commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
1929989
[processor/transform] Introduce optional metric name suffix setup for…
odubajDT 5dab8ba
fix tests
odubajDT cfdb468
duplicate chlog
odubajDT 284495c
Merge branch 'main' into transform-name-suffix
odubajDT fcfa77b
Apply suggestions from code review
odubajDT 4e19a21
Merge branch 'main' into transform-name-suffix
odubajDT 195e846
Merge branch 'main' into transform-name-suffix
odubajDT f19b12c
Merge branch 'main' into transform-name-suffix
odubajDT d637e42
Merge branch 'main' into transform-name-suffix
odubajDT 20f84d3
Merge branch 'main' into transform-name-suffix
odubajDT 751d949
Merge branch 'main' into transform-name-suffix
odubajDT 8b8e160
Merge branch 'main' into transform-name-suffix
odubajDT 3987386
Merge branch 'main' into transform-name-suffix
odubajDT 5e9023b
Merge branch 'main' into transform-name-suffix
odubajDT e4e4593
Merge branch 'main' into transform-name-suffix
odubajDT 396c2a8
Merge branch 'main' into transform-name-suffix
odubajDT fd38e0f
Merge branch 'main' into transform-name-suffix
odubajDT 8b6aeb6
Merge branch 'main' into transform-name-suffix
odubajDT c8731dd
Update .chloggen/transform-name-suffix.yaml
odubajDT 4cdb628
Merge branch 'main' into transform-name-suffix
odubajDT a30e1f0
Merge branch 'main' into transform-name-suffix
odubajDT 3e7f91a
Merge branch 'main' into transform-name-suffix
odubajDT 0748019
Merge branch 'transform-name-suffix-patch' of https://github.com/edmo…
edmocosta ea1be86
Change default suffixes to use previous separator "_"
edmocosta 8a3ae40
Merge pull request #125 from edmocosta/transform-name-suffix-patch
odubajDT 0c4b842
Merge branch 'main' into transform-name-suffix
odubajDT 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Use this changelog template to create an entry for release notes. | ||
|
||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | ||
change_type: breaking | ||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver) | ||
component: processor/transform | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: "Change default metric name suffix for convert summary and extract histogram functions according to OTel semantic conventions" | ||
odubajDT marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. | ||
issues: [33850] | ||
|
||
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: "Adaptations of the metric name suffix were made to match the latest OTel convention which uses '.' instead of '_' in suffix" | ||
odubajDT marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
# If your change doesn't affect end users or the exported elements of any package, | ||
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label. | ||
# Optional: The change log or logs in which this entry should be included. | ||
# e.g. '[user]' or '[user, api]' | ||
# Include 'user' if the change is relevant to end users. | ||
# Include 'api' if there is a change to a library API. | ||
# Default: '[user]' | ||
change_logs: [] |
odubajDT marked this conversation as resolved.
Show resolved
Hide resolved
|
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Use this changelog template to create an entry for release notes. | ||
|
||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | ||
change_type: enhancement | ||
odubajDT marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver) | ||
component: processor/transform | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: "Introduce optional metric name suffix setup for convert summary and extract histogram functions" | ||
odubajDT marked this conversation as resolved.
Show resolved
Hide resolved
odubajDT marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. | ||
issues: [33850] | ||
|
||
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: | ||
odubajDT marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
# If your change doesn't affect end users or the exported elements of any package, | ||
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label. | ||
# Optional: The change log or logs in which this entry should be included. | ||
# e.g. '[user]' or '[user, api]' | ||
# Include 'user' if the change is relevant to end users. | ||
# Include 'api' if there is a change to a library API. | ||
# Default: '[user]' | ||
change_logs: [] |
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
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.
@edmocosta @TylerHelmuth Now that the transform processor is beta, I'm wondering how we should handle this change. I can think of a few options, in order of most-abrupt to least.
On one hand, I'm okay being more aggressive since there's a clear and straightforward remediation path to retaining the old metric names. On the other hand, this change is "silent" within the Collector and won't go noticed until the user is seeing (or missing) data in their backend.
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.
Considering changing the metric names can impact so many things on the user's side (dashboards, alerts, etc), I think I'd go with the more conservative option, giving users some time to adapt, without breaking it.
I like the feature gate idea to control the default
suffix
separator (_
or.
). In addition to that, we could maybe log a message (at function bootstrap) when thesuffix.IsEmpty()
, warning users that does not read the release notes that the default suffix will be changed. Finally, we could update the functions docs examples to include the suffix args with the dot separator, so people that just copy & paste it during the transition time won't have issues when the new suffix format comes into place.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.
I do not have the capacity to deal with additional requests here, since the scope of the ticket changed, if somebody is interested please take over the PR, sorry
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.
No problem, thank you @odubajDT!
I think we could add the deprecation things later, this PR is around for a while, and releasing it with the suffix support would be a quick win IMO. If @evan-bradley agrees, we could just bringing the default prefix separator back to
_
, and tackle the prefix changes/deprecation 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.
That sounds good to me.
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.
Hi @odubajDT, I've opened an PR against your branch addressing these last requests (odubajDT#125), could you please kindly merge it so we can finish the review using your PR? If you don't have availability for that please let me know so I can open a new one. Thank you again!
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.
merged, thanks!