Brett McBride

https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/telemetry-stability.md#schema-file-driven-telemetry-producers - any of our instrumentations that are stable **should** have a fixed schema URL set, and it **must not change** (even if the semconv version does). There's some leniency...

Hi @jcchavezs can you give some info on what this is about? Has it come from a higher-level task to apply to all SIGs, or were we doing something wrong?...

In support of this proposal and as described above, PHP SIG uses `code.function`, `code.namespace`, `code.filepath` and `code.lineno` extensively throughout our auto-instrumentation packages. We find them very useful and would support...

I think that's a 422 response from the opentelemetry collector (or whichever service you are sending telemetry to). Is anything logged upstream if you dial up the logging?

I guess the first question is, can this be (or could it be in the future) an auto-instrumentation for more parts of react? i.e., the framework/ecosystem, rather than just this...

Two things are missing that I can see: - add to the top-level `.github/workflows/php.yml` so that the tests will be run - add to the top-level `.gitsplit.yml` so that we...

> Absolutely. The other half of the HTTP library is a server, so that’s an obvious choice for what to instrument next. Cool, that makes sense. I just wanted to...

> Should the examples stay where they are or move up to /examples? I think where they are is fine, it makes sense for them to be with the associated...

https://packagist.org/packages/open-telemetry/opentelemetry-auto-reactphp

> Just running into the exact same issue in a project I am working on. Is this on the horizon to be merged any time soon? No. I'm not sure...