-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/receivercreator] Make documentation clear on the effects of using the receiver across different signals #23014
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@atoulme Happy to help. I indeed got wrong the part about the Collector crashing. What I understand now from the previous PR is that a receiver instantiated in pipelines with incompatible telemetry types might not crash when they should? We need to get the following clear:
The existing note only partially covers the second item. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/receivercreator
Is your feature request related to a problem? Please describe.
See #19641 (comment)
Describe the solution you'd like
We should make sure the documentation is accompanied by a few examples to clarify the use case of using the receivercreator across different signals.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: