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

Name of the method appears mangled when result is kotlin.Result #573

Open
maxkomarychev opened this issue Jun 19, 2024 · 1 comment
Open

Comments

@maxkomarychev
Copy link

maxkomarychev commented Jun 19, 2024

Related links:

Expected Behavior

Name of the method should appear in the trace as is or as specified in the first arg of @NewSpan.

Actual Behaviour

The name appears with extra characters, given this code:

@Singleton
open class OneService {
    @NewSpan
    open fun hello(): Result<String> {
        return Result.success("hello")
    }
}

the name of the method in the trace appears like this:

name1

and when doing

@NewSpan("helloworld")

it appears like this:

name2

Steps To Reproduce

Set up a dummy service and a controller:

@Singleton
open class OneService {
    @NewSpan("helloworld")
    open fun hello(): Result<String> {
        return Result.success("hello")
    }
}

@Controller("/probes")
class Healthcheck(val oneService: OneService) {
    @Get("/health")
    fun health(): String {
        return "health" + oneService.hello().getOrThrow()
    }
}

Run jaeger:

docker run --name jaeger \
  -e COLLECTOR_OTLP_ENABLED=true \
  -p 16686:16686 \
  -p 4317:4317 \
  -p 4318:4318 \
  jaegertracing/all-in-one

Call the method: curl http://localhost:8080/probes/health

Observe wrong names in the trace.

Environment Information

  • macos 14.5 (23F79)
  • jdk 17

Example Application

No response

Version

4.4.2, 4.50

@maxkomarychev maxkomarychev changed the title Name of the method in the trace is mangled Name of the method appears mangled when result is kotlin.Result Jun 19, 2024
@natalie-zamani
Copy link

We're also running into this. It's effectively making troubleshooting issues via stack traces impossible for us, which is pretty bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants