Skip to content

Error stacktrace and Exception type not being set properly #7235

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

Open
agentCalculator opened this issue Apr 16, 2025 · 2 comments
Open

Error stacktrace and Exception type not being set properly #7235

agentCalculator opened this issue Apr 16, 2025 · 2 comments
Labels
area: instrumentation Related to an instrumentation package bug Something isn't working instrumentation: otelgrpc

Comments

@agentCalculator
Copy link

Image

Description

A clear and concise description of what the bug is.

Environment

  • Go Version: 1.22.0

  • otelgrpc version: v0.55.0

Not getting proper stacktrace of error instead getting stacktrace of the function calls making it difficult to debug.
It should show the stacktrace of where the error has occurred.

@agentCalculator agentCalculator added area: instrumentation Related to an instrumentation package bug Something isn't working instrumentation: otelgrpc labels Apr 16, 2025
@agentCalculator
Copy link
Author

agentCalculator commented Apr 17, 2025

@dmathieu

Can someone please guide me on this so I can debug this issue further and try to fix it
It gets difficult to debug errors and panics without the proper and relevant stacktrace

Thanks!!

@dmathieu
Copy link
Member

dmathieu commented Apr 17, 2025

It seems you have pinged folks at random. You're lucky, I'm a Go SDK maintainer, but please don't do that, as the other two pinged folks are not contributors to this repository.

I don't think this has an "easy" fix, if it has any at all.
The stacktrace is recorded within the SDK, here, and we get the stacktrace from the runtime.

We're getting this meaningless stacktrace due to how gRPC works in Go, and the fact that stats handlers aren't run in the same stack as the rest of your application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: instrumentation Related to an instrumentation package bug Something isn't working instrumentation: otelgrpc
Projects
None yet
Development

No branches or pull requests

2 participants