Skip to content

[exporter/elasticsearch] Profiling: Correctly interpret locations #40959

Open
@rockdaboot

Description

@rockdaboot

Component(s)

exporter/elasticsearch

What happened?

Description

The ES exporter does account the additional indirection when reading the locations of the Sample type.
The result is that stored stacktraces are completely wrong.

The Universal Profiling flamegraph demonstrates it:
Image

Collector version

f945dfd

Environment information

Doesn't matter

OpenTelemetry Collector configuration

Log output

Additional context

I have a fix locally and will open a PR soon.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions