Damien Mathieu
Damien Mathieu
Related: https://github.com/open-telemetry/opentelemetry-go/pull/6590 You have more context than me here, but I wonder if we need that configuration at all. In a not-too-far future, this config will only have one possible...
You can see a debug/demo distribution at https://github.com/dmathieu/tmp-profiles-collector/
Moving this PR back to draft, since it's blocked.
Should we then delete the @elastic/apm-agent-go team? Alternative: we could keep the owners file as-is, and change the members of the team?
cc @elastic/obs-ds-ebpf-go
If we don't want everyone from obs-ds-ebpf-go to get notifications, then keeping the team and changing its members seems like the best way.
I don't know about this. It could lead to unexpected performance issues Also, this would be a new feature and this repository is in maintenance only.
Rather than maintain a fork, have you considered migrating to OpenTelemetry? It doesn't have sensitive data redaction (though that's being worked on https://github.com/open-telemetry/oteps/pull/255), but it's way more modular than our...
Closing this, as the project does not accept new features, and this one could have performance issues.
They are the only valid way to make an unattached struct. As the comment mention, you should use `AppentEmpty()` from the parent slice, or set values within the default object...