Open Telemetry Uncategorized, 21 Dec 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2022-12-21 meeting

Description

OpenTelemetry PHP SIG Meeting

A

B

Hey Sherlock.

A

How are you good thank you? Do.

B

I'm living the dream: okay,.

B

There's the Aussie.

B

Hello, g'day Mr McBride. How.

C

B

Doing swimmingly, how are you.

D

C

Good! Congratulations on making it to the end of the year.

B

Geez you're not kidding, speaking of which Speaking of the end of the year, if no one else opposes the other six or all not meeting next week or the week after and I think we should do the same.

C

uh I was going to propose something similar, but yes, it's a great idea. Good.

B

Get uh get off the internet. uh What are the the new, the young kids these days say touch grass.

D

Oh I, like that one yeah.

B

That's a that's a new one to meet you but I like it.

D

B

All right, let me uh let me show my screen and we'll go through our leading notes, because I think we're the only three that I expect today.

B

Sure, I'm not sure any industry secrets you can see my seek meeting agenda notes. I can yes all right great.

D

Look for request.

B

Looks like somebody reviewed this bad boy already.

C

D

Yeah, it makes the work required on that one, a little bit.

B

uh The hotel SDK disabled to disable SDK, auto loading.

B

It's like it's device, commenting on this or are you serious yeah? He was yeah all right um into other is yeah. Let him continue with you on that, one and last, but certainly not least, you had default log into console hooked like he was talking with you on this one too.

C

C

D

Was a while ago.

C

So I don't think he has anything more to say.

D

C

B

You want me to review this, then. Yes,.

C

B

You got it it's in my queue, foreign.

B

It's like you did a beta update. It looks like this one's been approved already. I can approve and merge that after this video.

D

B

um That one's been saying that we should probably close this at some point.

B

Surprise, tailbot didn't close this oh and somebody commented on this today.

B

We will uh we'll see if Cedric responds and, if not we'll, take a look at that after the news.

D

D

D

B

Like zebra, oh the symphony, SDK I know that's right, though. I saw that one that would.

D

Be a good thing to do. I.

B

Think is this one yeah.

D

C

I'm not sure, if he's coming back yeah.

B

Yeah observing a problem.

B

All right now to the agenda items looks like you have a couple: Mr McBride, you all.

C

Right, yeah I do um um so we we had that that one person who was give me some weird things and and 32-bit support was- was sort of the the issue that he eventually identified, where what was the cause? um Well,.

B

One of well one of them too right. He was also using um php71 yeah.

C

Yeah so once we got past those ones on an actual supported, PHP version, which was version eight, it doesn't work on 30gb uh I was yeah.

D

I was worried, he was going to say you.

C

Know I can't upgrade I can't do 64. that evidently could um yeah.

D

Yes, the question was.

C

About is, is, is worth spending the time to support it. Is that a is that it should be doing that you know I mean. Is it popular?

C

um You know we can just enforce in composer that they have a 64-bit build, and that makes the problem go away for us until um yeah yeah until someone goes, complains more or provides some resources to to to fix it. I.

B

Think they're a compelling argument. Yeah. The answer to your question is absolutely not I. Think we're it's 2022 we're not supporting 32-bit systems. I just think it's. It's definitely not popular enough to waste the limited resources that we have, but it.

D

B

Does spark a very good question: I, don't think that we should necessarily restrict to 64-bit, because um we also might have to worry about arm at some point.

C

B

I haven't even I, haven't even considered if our builds run unarmed. It's definitely something we need to be testing so I'm glad. You asked this question not because of the 32-bit part, but because of the arm part.

C

Yeah yeah, that is interesting.

C

D

C

Something we could probably test that in Docker. Can you run an art, build.

B

I, don't know if you can test it in Docker because uh uh because of cross compatibility but I think that I I don't have an M1 yet and I'm getting one for work soon. But.

D

B

Think there is also AWS has gravity around instances and I think that um I think gcp has arm instances too. That's.

D

B

Yeah they have armed machines, so we could test some of those.

C

Yeah yeah I mean they're otherwise to test for um or any specific problem was, was sort of about. I.

D

Mean it was to.

A

C

Big problem, but it was inverse flow. You know you can you can test for the size of oh yeah if I need to jump instead of um specifically 64 beginners.

B

Yeah you're: this is we're talking about architecture and not it's uh yeah, I understood, um yeah, I, think that, from my perspective is hell no enough of uh response that should respond to or should we support, 32-bit yeah.

C

I think so yeah so yeah, but but maybe there's not a maybe we don't want to rule it out in code because we might there might be some collateral damage. uh Other architectures.

B

Yeah I mean that might be I guess to be to add something to the readme.

B

You must be 64-bit or arm if we decide that it works or whatever yep all right sounds good to me. um You updated the hotel demo. That's great news.

C

Indeed, indeed, uh I've just been approved by a few people now I've just hasn't been merged in, but.

B

I'm, just looking at.

C

Yeah beautiful I mean there.

B

Was it a big change.

C

A good thing, this change was actually removing lots and lots of code. Oh I assume um Auto instrumentation.

B

And php2, look at you go yeah, that's great loved! You love to see it.

B

So I should approved this too. That's important.

A

So the one question is this: a quad surface Auto instrumented only or it's uh maybe one.

C

Good question: no, it has a little bit of both. It has manual instrumentation and although okay.

A

B

Is actually probably ideal for the demo application.

B

Who knows Mr McBride? That's awesome! uh Genic year of the you're, the last one. Yes.

A

So uh recently, I had an interesting uh discussion with uh internal discussion in uh in my company regarding uh this Auto instrumentation coverage, and uh because now we we are supporting this psr18 and also https and calls but uh I'm wondering how many other you know external. I o codes we we could or should support, because there are this database calls and so on and I think that we, as we now have uh this support in C extension, so it top bias made a change.

A

It was uh only one line of code to to remove this limitation uh regarding instrumenting, only a user calls, and now we can also uh hook into into our other internal calls. So we can start also working I. Think on on support for this different IO calls. What do you think about it? And maybe you already started this. uh This work.

C

uh I started thinking about um instrumental database um yeah, it was just. It was hard to sort of pick. A candidate um I was thinking uh start playing with, um probably laravel's database I think it's called.

D

C

And um oh, it's the other one good morning, Doctrine Doctrine database abstraction um just because they're the two that we use most often in my day, job um yeah, so that that's a way to do it, but you also mentioned you know we could hook straight down into um something like PDO.

C

um As as well, um yes, I absolutely think that that we should um and that we have the capability to do it now. uh Are we just waiting for someone to have the time or the initiative to start prototyping it up and and finding out if it works,.

A

Yes, so I would like to avoid duplicate or work. Maybe we should create I, don't know uh some tickets in in GitHub to and then assign that to to specific people. Yeah.

B

What was the first Library you mentioned before.

C

Doctor, it's called eloquent, it's um uh laravels, a nice brother yeah. That's the one.

A

And another question: Brad: do you use uh I I know that you are using, in fact our Auto instrumentation for some internal apps that you are I, don't know developing or using yes, and uh from your perspective, do we have uh gaps in this Auto, instrumentation or uh or do what you see is is good enough for you.

C

um In terms of what it does for the slim framework, which is the the main um sort of library that we use I, think it's it's very good, it's maybe two verbose if anything um yeah, but the the next obvious, oh and- and we can obviously do um http calls now.

C

um I think I think that the next big gap um uh for us is databases. Yes,.

B

That's the thing that people usually want to instrument the most with observability, because usually the thing that takes the longest amount of time.

A

Yeah yeah yeah, that's right, yeah, yeah IO is definitely we.

C

Almost always spend your time in PHP, at least in in the sort of apps that I tend to deal with, and it's HTTP calls and it you know: you're calling a web service or something or an API, and it's database schools, mm-hmm.

A

Okay, so so the next steps probably would be to add some tickets and maybe start prototype prototyping. uh This work.

C

uh Yes, yes, um yeah.

D

C

It might also be worth just um putting a note on the auto instrumentation slack Channel.

C

um If, if we do start right, which is that yeah, it could just be I'm going to start prototyping this if anyone's interested, you know talk to me. Okay,.

B

I did want to add to that. The PDL object, the default php1 I bet you that's the one that is the most important, at least from my perspective, because it's built into PHP, but I think that eloquent and Doctrine probably are close seconds.

D

C

I feel like yeah, if you could get if you get PDO to work, that would work for lots and lots of database abstractions exactly.

B

Yeah I think that would be a good. uh Is the right, I guess the right phrase. There would be a good gold standard for uh throw database, instrumentation or durability.

C

Yes, yeah, yes, I, agree um yeah. It could also be hard to do as well, because um and yeah I've been thinking about it, but haven't really written any codes yet. But but when you look at how um something like PDO works, you kind of you've got a call to maybe prepare a query and then once you've got your query, object, read uh sort of connection object. You've got another one to execute it, and um you know it's a multi-step process. I guess! So. How do you heavy rep, Auto instrumentation about that I'm?

C

Not sure yet? But that's why we're going to get on Prototype.

D

A

Yeah but video is another uh extension native extension right. Yes,.

C

A

So when we uh doing Auto instrumentation for that we should um it seems that we should support uh many different databases. Correct yes,.

C

Yes, that's right, and so, if we, if you know any any um database, abstraction Library, um would all support PDO. So there's there's a PDO, flavor or buried for most databases and there's usually a native one as well so.

D

C

Know we get like 50 percent of all database Well we'd have probably 100 coverage of all databases and then 50 of the implementations for those databases.

A

Okay uh and to accept uh databases, uh are there any other methods uh to do external calls? I mean except the ones that we are supporting already um uh this psr18 and uh async HTTP calls.

C

Maybe maybe cues is another one. People tend to use those a lot, but they also tend to be very fast.

A

B

Same yeah same with any like uh distributed, Q value Source, another big one and those are really fast too, like adding observability to those is uh that's often not very important, because the calls are oh.

C

What about what about non sort of PDO supported databases like I'm thinking, redis and Bongo? Oh.

B

That's what I was just talking about well I'd, say: oh you're, talking about restaurants but like uh no, but just not the simple key value, but I have a lot of other things, but you're talking about a good transactional. Where this thing are you talking about something else, but.

C

Yeah uh I lost you a bit there, but um what was I talking about um foreign.

B

I think that those things are not nearly as high on our uh totem pole of importance for observability uh as databases.

B

There's a reason: it's called land because everybody uses those four products.

D

Together very specifically, and the evidence should be instrumental.

C

Yeah yeah I would agree with that. um Yeah.

D

C

I would probably favor if we can, if we can make it work, PDO would be the most useful, widely useful thing that we could that we could do for the for the databases of IO.

A

B

Wordpress but that's another discussion for another day.

C

uh We appreciate you know we're talking about that. The.

B

Other day yeah, oh.

A

C

Told you about that. Yes, yes, I'm, really excited about the idea of that I think that would be a good um I was gonna, say, holidays activity, but um yeah, maybe I do need to take a break. You know.

B

Yep I feel about you.

B

D

B

D

B

It is and uh for sure you're going to start working on some of the tickets for that.

A

uh Yes, but uh I'm not sure that I will be available next week, so.

B

That's okay, we're all playing taking a little break.

A

Yeah yeah yeah happy.

B

Holiday, do you, are you all celebrating the holidays by you for sharing.

A

uh Yes, yes, good.

B

Good get some, we all need some rest and Recovery I'm. Sure. Yes,.

C

Please please take some time off yeah, we hope not to hear from you for a week or so. Yes, that's right.

B

B

Right anything.

D

B

Want to discuss today.

A

Does it from me not me.

B

All right, well, then, I hope you all have a wonderful vacation and we'll catch you, let's I'm pulling up my calendar now to say what date we're gonna have the next meeting.

D

Let's see, there's my calendar.

B

So I guess our next meeting will be on January 4th.

A

um I think so: okay.

C

Well then, yeah be around for that me.

B

Too then uh I can use the classic corny. Dad joke. We'll see you all next year.

C

Wow fabulous all.

B

Right we'll talk, I'll talk to you all, then all right, bye-bye.

A

Thank you, bye.