> Larry > Accidentally replied to Larry's message privately, but there's value in it > being here: > > > So the idea would be an interface on top of the official library, so > there's some PSR<-->official library bridge > > For the most part... yes. > My understanding is whilst OTEL does split the actual interfaces (API) and > implementation (SDK), to allow libraries to send signals without requiring > the full SDK, it does not seem to be encouraged to write your own > implementation. > This PSR would serve as a subset of the API, providing a minimal base for > interop. > > My thoughts are given most providers are following the > trace->span->subspan layout, we could get in integrated to client libs for > sentry without too much work. > Rather than the possible full rewrite that going full OTEL would require > (since that would essentially mean throwing away current implementations, > in exchange for writing an exporter). > From a frameworks perspective, it could be seen as *too much work* > to implement the full OTEL API or SDK, so, the PSR would allow frameworks > like Laravel to *just* resolve an instance of the Tracer, and give it some > info > > If that is what you would see as PSR<-->OTEL Bridge, then yes, it is > indeed :) >
This sounds like deficiencies of the PHP OTEL API and SDK. Maybe the working group can act as stakeholders or case studies for the OTEL authors? I've contributed in the past to OTEL and could do so again so I'm not volunteering others to work on something :) > > Ah, so the PSR intent is be basically "OTEL Jr" to make eventual > transition to a common API easier? > > In that case I'd recommend ensuring that it's open for future PSRs to > extend as more parts of OTEL standardize. > > Yeah, OTEL Jr sounds like a good way of describing it! > Long term, I'd expect the PSR to be used for "lightweight" tracing > purposes, and then if frameworks need to add even more info, they can > (without many/any BC breaks) migrate to the full OTEL lib should they need. > It would be helpful to have some examples of what this lightweight tracing is and is not. -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/2e20048c-7efe-4267-85c0-f0dab8211e83n%40googlegroups.com.
