-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Add an option to force using hostname instead of FQDN in the resource detection processor #5064
Conversation
|
Also @hprajapati-splunk you need to sign the CLA so that we can accept your contribution, PTAL at the bot message above! |
…em_source) as per review comment
…stname_sources) as per review comment
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.
Thanks for bearing with us on the review :) Behavior-wise this looks good to me but I left a couple of minor comments about the code. Also, note that CI will be broken until #5076 gets merged (sorry about that!)
… for System detector
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.
Looks good, thanks again! I would like @dmitryax to have a look at it too
@dmitryax PTAL also set the "ready-to-merge" label when you are done :) |
65be6ed
to
a170b2c
Compare
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
This includes changes to support optional types: - update sed script to update optional type to oneof - bump proto to 0.15.0 - make genproto - update sum to OptionalType - InstrumentationLibraryMetrics -> ScopeMetrics - InstrumentationLibrarySpans -> ScopeSpans - InstrumentationLibraryLogs -> ScopeLogs
Description:
This PR adds an option to force using hostname instead of FQDN in the resource detection processor.
Users can set
hostname_sources
to["os"]
to force the processor to use 'hostname'.This is an opt-in functionality so there are no breaking changes to existing user configurations
Testing:
Existing unit tests have been updated and new unit tests have been added to cover new changes.
Documentation:
README has been updated to show how to use the new custom 'system' configurations