Hi Adam, yes, please add my name. Happy to help on this PSR.
Regards, Enrico Il giorno dom 27 mar 2022 alle ore 16:00 Adam Allport <a...@allport.me.uk> ha scritto: > 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 :) > > > 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. > > > Enrico > That's fantastic to hear! > I'll add your name to the list of WG members if you're okay with that? > The chat is yet to be created, I believe that will happen after the > acceptance Vote > > > Thanks for your feedback everyone! > > > On Friday, 25 March 2022 at 20:37:18 UTC ezimuel wrote: > >> Hi Adam, >> >> as representative of Elastic and PHP FIG I'm very interested in >> supporting this PSR. I can promote it for the PHP projects in Elastic, >> including the APM team. >> >> Regards, >> Enrico Zimuel >> >> >> Il ven 25 mar 2022, 18:08 Adam Allport <ad...@allport.me.uk> ha scritto: >> >>> 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 >>> >>> >>> On Friday, 25 March 2022 at 03:18:40 UTC Ken Guest wrote: >>> >>>> I think the strategy here is to come to a Standard before those >>>> frameworks/solutions solidify to a state where it might be more awkward to >>>> come to a common ground. >>>> >>>> I'm open to correction of course ;-) >>>> >>>> On Thu, 24 Mar 2022 at 15:56, 'Levi Morrison' via PHP Framework >>>> Interoperability Group <php...@googlegroups.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> I am not particularly knowledgeable about how PSRs are developed. I am >>>>> chiming in to say that it seems a bit premature to write a PSR for this. >>>>> The OpenTelemetry SDK for PHP is pre-alpha and OTEL itself is not even >>>>> considered GA. Are you sure the time is right? I am very interested in >>>>> OTEL >>>>> and the impact it can have in the PHP ecosystem, but want to make sure the >>>>> effort is put in the right place at the right time. >>>>> >>>>> Full disclosure: I have previously contributed >>>>> <https://github.com/open-telemetry/opentelemetry-php/commits?author=morrisonlevi> >>>>> to >>>>> the OTEL for PHP project and work for Datadog. >>>>> >>>>> -- >>>>> 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 php-fig+u...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/php-fig/39629ac6-ef99-46e0-a6f1-e0653d17246fn%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/php-fig/39629ac6-ef99-46e0-a6f1-e0653d17246fn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> >>>> >>>> -- >>>> http://about.me/kenguest/ >>>> >>> -- >>> 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 php-fig+u...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/php-fig/028f1716-1b46-42a1-9497-e2153be6c758n%40googlegroups.com >>> <https://groups.google.com/d/msgid/php-fig/028f1716-1b46-42a1-9497-e2153be6c758n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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 php-fig+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/php-fig/6c5fea64-4fff-43be-9619-4e3534520336n%40googlegroups.com > <https://groups.google.com/d/msgid/php-fig/6c5fea64-4fff-43be-9619-4e3534520336n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 php-fig+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAOMtwbT7ZzD8q7Jpd3R4W-EJWpddz2E3SvBPv2XkXnVKL8yR6w%40mail.gmail.com.
