Florian Lehner
Florian Lehner
> A question on timestamp encoding - what if I want to capture timestamps and each sample has fixed weight but it's not 1 - say, it's 100. With #649...
`TraceReporter` provides multiple independent options to report a trace. ``` type TraceReporter interface { // ReportFramesForTrace accepts a trace with the corresponding frames // and caches this information before a...
With the merge of https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/520 profiling will start to auto-tag versions to show development on a monthly base, starting July 1st.
As a side note, on the SemConv side there are discussions already happening around MCP. E.g. https://github.com/open-telemetry/semantic-conventions/pull/2083
Hi @lgwozdecki At the time of designing and implementing probabilistic profiling, its default values were fitted to the backend, that was used back then. In general, to keep the statistical...
At the moment, there is a conflict between `Profile.SampleType`, `Sample.Value` and `Sample.timestamps_unix_nano`. The resolution of https://github.com/open-telemetry/opentelemetry-ebpf-profiler/issues/63 was to have the same number of `Sample.Value` as `Profile.SampleType` - this might conflict...
Closing as resolved with the [changes to the protocol in v1.8.0](https://github.com/open-telemetry/opentelemetry-proto/blob/v1.8.0/opentelemetry/proto/profiles/v1development/profiles.proto) and its [implementation](https://github.com/open-telemetry/opentelemetry-ebpf-profiler/commit/ef2ca14e9171dea966ddb528bb75051039d4cdd4) in this code base.
Using Docker (to retrieve the Kernel images) inside of Docker, as in https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/985, revealed some challenges. Therefore closing this issue.
The process executable name is always set - independent of the frame type: https://github.com/open-telemetry/opentelemetry-ebpf-profiler/blob/20153416e82fc8ea4cc6016f1c72f7fa3cce473b/reporter/internal/pdata/generate.go#L256-L257 For interpreted frames, including Go, the build ID of the executable, that is required for post...
If a Go process uses cgo to call out to dynamic loaded parts, like `libc.so.6`, then these specific frames are handled as native frames. And for native frames, the mapping...