-
Notifications
You must be signed in to change notification settings - Fork 486
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
Clarify usage of otelcol.processor.discovery #5378
Clarify usage of otelcol.processor.discovery #5378
Conversation
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.
One small suggestion for the docs input
docs/sources/flow/reference/components/otelcol.processor.discovery.md
Outdated
Show resolved
Hide resolved
…very.md Co-authored-by: Clayton Cornell <[email protected]>
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.
Docs are OK as-is
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.
Docs look good to me and I always appreciate additional usage guidance 🚀
* Clarify usage of otelcol.processor.discovery Co-authored-by: Clayton Cornell <[email protected]> (cherry picked from commit 3627c89)
* Clarify usage of otelcol.processor.discovery Co-authored-by: Clayton Cornell <[email protected]> (cherry picked from commit 3627c89)
* Clarify usage of otelcol.processor.discovery Co-authored-by: Clayton Cornell <[email protected]> (cherry picked from commit 3627c89) Co-authored-by: Paulin Todev <[email protected]>
* Clarify usage of otelcol.processor.discovery Co-authored-by: Clayton Cornell <[email protected]> (cherry picked from commit 3627c89) Co-authored-by: Paulin Todev <[email protected]>
PR Description
As #5306 shows, there has been some confusion regarding
otelcol.processor.discovery
, discovery components, and OpenTelemetry semantic conventions. I hope that this new addition to the docs will clear the confusion for future users.Which issue(s) this PR fixes
Fixes #5306