On Fri, Mar 25, 2022, at 12:08 PM, Adam Allport wrote: > Hi All, > > I agree with Ken there! (But great question) > > Additionally (and with no intent to diminish the work of the OTEL team > so far), getting some of the larger players (Sentry > <https://github.com/getsentry/sentry-php/tree/master/src/Tracing>, > Elastic <https://github.com/elastic/apm-agent-php>, DataDog > <https://github.com/DataDog/dd-trace-php/tree/master/src/api>, etc) to > adopt the OTEL lib for creating tracing signals may be difficult due to > the large scale changes. > By creating this set of interfaces we will allow various frameworks to > implement a standardised set of signals to all of the other libs > (should they wish) can subscribe/contribute to! > I note my use of the term "loosely modelled" as opposed to "strictly > follows" > > As per Larry's suggestion, I'll write this up in more detail as a "Why > bother" section shortly! > > Thanks > Adam
So the idea would be an interface on top of the official library, so there's some PSR<-->official library bridge, as well as however many other implementations people feel like creating? If so, having people from the official library involved sounds like a good idea. --Larry Garfield -- 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/9f37d0e8-3250-417b-9642-bb46bb6e754c%40www.fastmail.com.
