Florian Lehner

friendly ping @open-telemetry/technical-committee - can you provide some feedback why this change shouldn't move forward?

Thanks for your answer. I did come along https://github.com/cncf/foundation/blob/main/recommendations-for-attribution.md#scope-and-nature-of-dependencies and `Use case 3: Build-time dependency` as well, before opening this issue. For this use case it is said: ``` In...

At the moment open-telemetry/opentelemetry-ebpf-profiler does not provide releases and licences of dependencies are part of the repository - see https://github.com/open-telemetry/opentelemetry-ebpf-profiler/tree/main/LICENSES This should meet the requirements for CNCF at the moment....

`Location.TypeIndex` will be removed with https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/167/ and replaced with semantic convention attributes.

Closing as resolved with https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/167

Closing this issue as with the [fileexporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/fileexporter) and the distribution demo @dmathieu shared it is possible to write data to file.

We had to take down the downloads for a moment and we are working hard on bringing them back.

Hey 👋 Glad to hear this package helps you. From the top of my head, I can't name a reason for ENOENT at this point. Maybe the queue is overloaded...

Could you provide a minimal reproducible example?

Can you check and log the returned error for [d.nfq.SetVerdict()](https://github.com/aojea/kindnet/blob/c547a9a7c20cd18fb49e5e8771cbf6200a6bd866/pkg/dnscache/agent.go#L200C3-L200C19)? I'm wondering if this reveals more information.