-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[processor/routing] Collector crash #26462
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
Labels
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
jpkrohling
added a commit
to jpkrohling/opentelemetry-collector-contrib
that referenced
this issue
Sep 5, 2023
This PR changes the routing processor so that it properly creates new instances of pdata.Span and InstrumentationScope, avoiding crashes later on due to nil pointers. Fixes open-telemetry#26462 Signed-off-by: Juraci Paixão Kröhling <[email protected]>
This was referenced Sep 5, 2023
jpkrohling
added a commit
that referenced
this issue
Sep 6, 2023
This PR changes the routing processor so that it properly creates new instances of pdata.Span and InstrumentationScope, avoiding crashes later on due to nil pointers. Fixes #26462 Signed-off-by: Juraci Paixão Kröhling <[email protected]> --------- Signed-off-by: Juraci Paixão Kröhling <[email protected]>
This was referenced Sep 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Component(s)
processor/routing
What happened?
Description
Collector crash, caused by misuse of the ptrace.Span construct by the routing processor.
Steps to Reproduce
telemetrygen traces --traces 10000 --otlp-insecure --otlp-attributes='attr1="demo",attr2="xxx"'
Expected Result
No crashes.
Actual Result
Collector version
0.84.0
Environment information
Environment
OS: Fedora release 38 (Thirty Eight)
OpenTelemetry Collector configuration
Log output
Additional context
Logs from telemetrygen:
The text was updated successfully, but these errors were encountered: