Skip to content

Tracer.startSpan should support overloads to parameterize messages #177

@carterkozak

Description

@carterkozak

What happened?

We do a great deal of unnecessary string concatenation in span names which can be completely avoided for unsampled traces:

String operation = "Jersey: " + requestContext.getMethod() + " " + path;

What did you want to happen?

Slf4j style overloads to construct trace strings only for sampled operations

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions