Proposal: Go Compile Time Instrumentation SIG

[ralf0131]

This is a proposal to establish the Go compile time instrumentation SIG. The background has been discussed in #1961. A consensus has been reached among GC/TC members, Go maintainers and multiple interested vendors.
We believe that the Go Compile Time Instrumentation SIG ensures that Go applications benefit from standardized, vendor-neutral, high-quality observability solutions that are both robust and easy to implement. Having one single, standard tool removes decision points from prospective developers, which makes the path to observability shorter & easier.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: trask / name: Trask Stalnaker (7cd35a1)
• ✅ login: ralf0131 / name: Huxing Zhang (0218e81, 81f34cd, 4e44b15, 9f287a0, b0fb2ff)

[123liuziming]

I approve!

[NameHaibinZhang]

I approve!

[trask]

@123liuziming @NameHaibinZhang @y1yang0 can you please review the changes and approve it if it looks good to you (instead of only leaving a comment)? thanks

[123liuziming]

LGTM

[123liuziming]

@123liuziming @NameHaibinZhang @y1yang0 can you please review the changes and approve it if it looks good to you (instead of only leaving a comment)? thanks

Sorry, I do not realize that I have the access to approve, thanks!

[Cirilla-zmh]

LGTM

[jpkrohling]

my comment/suggestion isn't blocking, I'm happy to sponsor this SIG!

[danielgblanco]

Should this project proposal include mentions of the two donation proposals that will be considered as part of this work? The one from Alibaba in #2344 and Datadog in #2497

I think it's awesome that we can get the best learnings from each and provide the community with a unified approach. Would love to see it reflected here.

[ralf0131]

Should this project proposal include mentions of the two donation proposals that will be considered as part of this work? The one from Alibaba in #2344 and Datadog in #2497

I think it's awesome that we can get the best learnings from each and provide the community with a unified approach. Would love to see it reflected here.

How about adding the following content to the end of the proposal

Reference

The project is a joint effort of donation proposal coming from Alibaba and Datadog. The proposals are listed as follows:

• [Donation Proposal]: compile time instrumentation for golang #2344
• [Donation Proposal]: DataDog/orchestrion - Compile-time instrumentation for golang #2497

[danielgblanco]

I think that'd be great @ralf0131

[ralf0131]

I think that'd be great @ralf0131

All the suggestion are applied.
Unfortunately the CI fails and it looks like there is a dead link found in project/event-api.md file which is beyond the scope this proposal. Any ideas how to fix it?

[pdelewski]

Should this project proposal include mentions of the two donation proposals that will be considered as part of this work? The one from Alibaba in #2344 and Datadog in #2497
I think it's awesome that we can get the best learnings from each and provide the community with a unified approach. Would love to see it reflected here.

How about adding the following content to the end of the proposal

Reference

The project is a joint effort of donation proposal coming from Alibaba and Datadog. The proposals are listed as follows:

• [Donation Proposal]: compile time instrumentation for golang #2344
• [Donation Proposal]: DataDog/orchestrion - Compile-time instrumentation for golang #2497

I think, we could also mention that goal is also to replace https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/instrgen

[ralf0131]

I think, we could also mention that goal is also to replace https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/instrgen

Sure. How about this?

The project is a joint effort of donation proposal coming from Alibaba and Datadog to replace Instrgen. The proposals are listed as follows:

• [Donation Proposal]: compile time instrumentation for golang #2344
• [Donation Proposal]: DataDog/orchestrion - Compile-time instrumentation for golang #2497

[trask]

Unfortunately the CI fails and it looks like there is a dead link found in project/event-api.md file which is beyond the scope this proposal. Any ideas how to fix it?

fixed in #2503 and merged latest into your branch, should be fixed now