-
Notifications
You must be signed in to change notification settings - Fork 489
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
feat(otelcol/extension/jaeger_remote_sampling): resync defaults with upstreams #6763
Closed
hainenber
wants to merge
4
commits into
grafana:main
from
hainenber:resync-defaults-for-jaeger-remote-sampling
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
c2cb89c
feat(otelcol/extension/jaeger_remote_sampling): resync defaults with …
hainenber 439aab9
Merge branch 'main' into resync-defaults-for-jaeger-remote-sampling
hainenber a5e3a36
chore(doc): update CHANGELOG entry
hainenber 4fc0733
fix(otelcol/extension/jaeger_remote_sampling): resync unit tests
hainenber 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 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 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 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 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.
I think this might be surprising to users, as suddenly telemetry might be not be able to get pushed anymore.
Looking at the upstream docs I think the default is 0.0.0.0 for this reason. Can we align it with that value?
Once we start supporting OTel Collector feature gates (eg. such as
component.UseLocalHostAsDefaultHost
) then it might make sense to also support this.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.
@tpaschalis If you look at this discussion upstream, they're working towards changing the default to 127.0.0.1 in a future release. Currently if you enable a specific feature gate (
UseLocalHostAsDefaultHost
) then all the components default to 127.0.0.1 instead.I think we need to figure out if we're going to do this before 1.0, since it would be a breaking change when it does get implememnted.
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.
Since this is pretty breaking, maybe we can park this one and accept the deviance as part of
grafana/agent
features. Not sure how we can reconcile with upstream for this one.