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

[exporter/Datadogexporter] Use Agent modules for validating hostname #34030

Conversation

dineshg13
Copy link
Member

Description:
Use Agent modules for validating hostname

Link to tracking Issue:

Testing:

Documentation:

@dineshg13 dineshg13 requested review from mx-psi and songy23 as code owners July 11, 2024 02:15
@dineshg13 dineshg13 requested a review from a team July 11, 2024 02:15
@github-actions github-actions bot added the exporter/datadog Datadog components label Jul 11, 2024
@dineshg13 dineshg13 changed the title Use Agent modules for validating hostname [exporter/Datadogexporter] Use Agent modules for validating hostname Jul 11, 2024
@mx-psi mx-psi added the Skip Changelog PRs that do not require a CHANGELOG.md entry label Jul 11, 2024
Copy link
Member

@mx-psi mx-psi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good, can approve once CI passes

exporter/datadogexporter/go.mod Outdated Show resolved Hide resolved
@@ -10,5 +10,7 @@ import (
)

func TestMain(m *testing.M) {
goleak.VerifyTestMain(m)
goleak.VerifyTestMain(m,
goleak.IgnoreAnyFunction("github.com/cihub/seelog.(*asyncLoopLogger).processQueue"),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this? Can you add a tracking issue?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@crobert-1 Could you help us with the best way to deal with this? (e.g. is there a template for tracking issues?)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see a need to track it.

We aim to have no leaks at all in the Collector, this should be tracked and eventually fixed in the Agent.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Created internal jira to track this work in Agent.

Copy link
Member

@crobert-1 crobert-1 Jul 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add frequency and information to this issue: cihub/seelog#182

Also, please add a reference in this file to that issue so that we have future context for why this ignore is necessary.

Since this goroutine is started during a dependency's init(), there's nothing we can do if we need to import the package that depends on it. It's okay to ignore for now.

@mx-psi mx-psi requested a review from crobert-1 July 11, 2024 14:36
@songy23 songy23 added the ready to merge Code review completed; ready to merge by maintainers label Jul 12, 2024
@mx-psi
Copy link
Member

mx-psi commented Jul 12, 2024

@crobert-1 will wait until Monday in case you want to review

@mx-psi mx-psi merged commit 6a5b9e6 into open-telemetry:main Jul 12, 2024
161 checks passed
@github-actions github-actions bot added this to the next release milestone Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exporter/datadog Datadog components ready to merge Code review completed; ready to merge by maintainers Skip Changelog PRs that do not require a CHANGELOG.md entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants