firstParty/native flag for elixir/erlang/go

[haidong]

To address #4795, this is part of a series of PRs that add isFirstParty or isNative flags to instrumentation registries that lack them.

This batch touches Elixir, Erlang, and Go instrumentation registries.

There are a number of repos that belong to individual maintainer as opposed to a corp/foundation entity. Please point out any errors and I will correct.

Oh, about where I placed the line: if there is a package: line, then the flag is placed right above it. Otherwise, I placed it under the createdAt: line, which makes it usually the last non empty line of the file. I did it this way before I observed this pattern in other files before modifications.

Thanks!

[svrnm]

Thanks for taking a look into this, note that there are many you marked as first party that aren't. I tagged some of them but not all.

A first party instrumention is given if and only if the instrumented library and the instrumentation library are created by the same party

A native instrumentation is given if and only if the instrumented library does not need an external instrumentation library and comes with otel out of the box.

[svrnm]

Suggested change

	isFirstParty: true
	isFirstParty: false

[svrnm]

that repo URL is incorrect, but also I don't think this is first party

[haidong]

What would be the correct URL? And how do you find it?

[svrnm]

that repo URL is incorrect, but also I don't think this is first party

[haidong]

What would be the correct URL and how do you find it?

[svrnm]

@haidong please take a look

[haidong]

@haidong please take a look

working on it now. Should be able to resolve your questions today.

[haidong]

Thank you, @svrnm !

I accepted your suggestions one by one first in the Conversation tab. I then found I could do it in bulk at Files Changes tab, which is what I did to the rest of your suggestions.

Please take a look again.

[svrnm]

/fix:all

[opentelemetrybot]

You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/10809519051

[opentelemetrybot]

fix:all was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

[haidong]

Please let me know if I can help in resolving the remaining conflicts. Thanks!

[svrnm]

Please let me know if I can help in resolving the remaining conflicts. Thanks!

those files have been deleted, since Go SIG is no longer maintaining them, so to resolve the conflict work on your PR locally, merge from main and make sure those fails stay removed.

[haidong]

those files have been deleted, since Go SIG is no longer maintaining them, so to resolve the conflict work on your PR locally, merge from main and make sure those fails stay removed.

Done. Please review when convenient. Thanks @svrnm

[haidong]

I noticed the Links / REFCACHE updates error. Following the suggestion, I ran npm run test-and-fix but it failed with the following:

...
> _build
> npm run _hugo -- -e dev --buildDrafts --baseURL "${DEPLOY_PRIME_URL:-http://localhost}"


> _hugo
> hugo --cleanDestinationDir -e dev --buildDrafts --baseURL http://localhost

Error: Unable to locate config file or config directory. Perhaps you need to create a new site.
       Run `hugo help new` for details.

Total in 0 ms

Help please, thanks!

PS. After reading https://opentelemetry.io/docs/contributing/pr-checks/, I ran npm run check:links with the same results.

[haidong]

/fix:all

[opentelemetrybot]

You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/10865154166

[opentelemetrybot]

fix:all was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

[haidong]

/fix:all

[opentelemetrybot]

You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/10871784541

[opentelemetrybot]

fix:all was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

[haidong]

Thanks so much @svrnm for your feedback and patience.

If you have no objections, I'll proceed with the rest instrumentations. I'll once again do it in batches, a few programming languages at a time, so the number of files touched won't be overwhelming.