Open Telemetry Uncategorized, 15 Sep 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2022-09-15 meeting

Description

Open cncf-opentelemetry-meeting-3@cncf.io's Personal Meeting Room

A

Hey nacho, that's weird, my front. Camera is not working.

A

Hey: hey there, how are you good? How are you doing.

B

Fine okay, I finally found the the problem in your peer. Oh passing, the test.

A

Yeah, I know I I saw it too yeah.

B

Okay, I I was checking last week and I was expecting to see you in the meeting. It was last week right, yeah and I just forgot about it later, so I have been checking before and it's just strange because in local it works, probably because the version of xcode is handling the project in a different way. uh But yeah in the did have action. It was failing always so uh you you wanted it to be merged.

A

Yeah, um okay, I guess the the the the hiccup that I was seeing is. It looks like we need to regenerate the protobufs okay um and I'm not sure how to do that. So that's what I was. I was waiting for this meeting to talk about that.

B

Oh okay, so you do you need that on the met and the metric.

A

um Well so, uh let's see, let me pull up the pr here.

A

Oh, it's working now look at that interesting.

B

A

Did you, oh, you did update it. Okay,.

B

Yeah I fixed- I, I don't know that they oh fix it.

B

A

Guess so yeah, that's bizarre! Okay! Well! Yeah! I didn't know. I could.

B

I could fix a an external pl, okay yeah, so I saw.

A

I saw that and I thought um I thought, that the uh version of the um generated like uh okay open you know the protobufs for the uh hotel, otlp exporter. Okay, I thought that that needed to be regenerated. So, okay, yeah, that's great. Let's merge it.

B

Yeah, okay, it was.

B

A

B

Know why it for my computer. It worked perfectly I checked last week also, and I.

A

Had to get it, I was working. It's fine, too yeah.

B

I don't know how, uh depending probably on the version it finding the that framework, but it's not finding that in github yeah.

A

B

It's not, I mean it's not defined as a dependency yeah.

A

B

On the project uh switch.

B

So I mean it should fail everywhere, because it's not in the in the definition uh of the of the package but yeah okay.

A

So then I can I can it's in it's in my package resolved though maybe it's in your package resolve.

B

uh For I mean it's in the package resolved, but it's not in the target that.

A

You're importing.

B

A

All right right, okay,.

B

And the the thing is that it should fail. uh I mean it should fail for in all places, because it's not in the dependencies I mean. uh I don't know why it's not failing locally, because it should be added to the dependencies as one of the packages to import as it has in the open, telemetry exporter.

A

B

You know what I mean right.

A

B

uh Yeah yeah, I don't know why, but it's now. It's.

A

Working, it was really weird.

B

I have the last week I downloaded it. I saw that you updated also with main just and yeah okay. So then I think I can merge this. uh Do you prefer a squash and murders.

A

Yeah yeah, I think that's okay, yeah clean it up. I think that's a great idea.

B

B

Yeah, I think it's probably better when you are adding some squash and merch. Let me just.

B

B

Okay uh yeah. Let me.

B

I will open the document.

B

B

Let me yeah, yes, I decided, but there are no things here, not even updated. This.

B

So yeah, uh okay! So with that, do you want a version for with, uh with with that change,.

A

Yeah, I think that would be great um okay. We can probably also merge your url instrumentation um improvements.

B

Yeah I was waiting for your pr because, if I messed mine you will have to update your branch again uh because it's configured, so you cannot merge without being up to date. Yeah.

A

B

With the main branch, so yeah.

A

B

A

Just updated your branch, so it should be.

B

A

Once it's done, building.

B

Great uh yeah we can merge that and create a version yeah, because the session instrumentation was taken, probably one. Second, almost oh.

A

B

A

On the project.

B

It could take uh up to a second, I would say yeah.

A

Yeah, the the when you when you iterate over that class list, it's a linear yeah with how many classes there are so the more classes longer it takes.

B

Yeah for a bigger project, it could be quite expensive.

A

Yes, yeah at least.

B

Now it's done uh unparalleled uh and.

A

B

Reduce the time yeah, uh so, okay uh for the rest, uh yeah, I don't know um yeah. I was talking a bit with do you know about the active span with my colleague at the our dock, who had that issue and- and he told me that his issue was happening while running the app every time.

B

Every time the metal compiler did things which mean that for his project, whose flatter-based code was updating the metal because of the ui is updated, uh so it was building it every time. So that's a limitation that probably we should uh yeah take care about. uh So I don't know if it's related to yours to your issue, but I think you are not. I don't know if you are linking something that could be updated, metal yeah, I don't know, I will call it the metal compiler. I mean.

A

I mean I'm just using swift ui like maybe maybe it is under the hood yeah. I don't know yeah.

B

Okay, that, okay, then that's a clue. uh Yeah, probably we. I can try with a a simple swiss ui app to see if it breaks somehow or or something like that.

B

I just okay yeah, probably it's only building at the beginning. So it's why yeah.

A

It's resetting.

B

It uh before loading, uh but maybe it updates the shaders it compiles the shaders. Also during the app run uh yeah then then we should probably open an issue somehow yeah. If it's doing that.

B

Let's see but yeah.

A

B

Os activity right.

A

B

Yeah, it's not a very much used api, but.

A

B

It for uh the async await thing so.

A

I wonder if there's like a way to create like a sub group, you know, like um I, don't know what the terminology is come on.

A

Like maybe, if we created like a new, um because I think like it, it uses the current activity.

B

A

um If we seated it with like our own, like activity, sub subgroup like maybe it can um get outside of like the os activity scope like if we enter a new scope like for the for the um instrumentation.

B

uh Is there a way to group the os activities things well.

A

So there's this.

A

B

A

I I'm not entirely like. I don't have my head totally wrapped around it, but okay, yeah and let me send you this. um This function.

A

Why is this number.

B

Yeah, oh I'm in the wrong yeah. One of my concerns was that using us, os activity uh could mean that sometimes it will fail yeah, because people could be using uh things related to that yeah for for uh real reasons. So we we are able to navigate one level up so yeah. There are some situations where it wouldn't never work, but so have you said something I don't know.

A

I sent it to you through slack.

B

Oh okay, sorry yeah. It wasn't another.

A

Oh oops, no, no.

B

A

B

uh Scope enter yeah, but this is the the yeah. This is what we are already using. Oh.

A

Are we already using this okay yeah.

B

We we enter an exit scope when we create a uh when we create a spam.

A

Right right, but I was.

B

A

Like once like, if we initialize the whole system, rather than just putting it, on top of the existing scope, create a new scope for everything. Yeah.

B

A

Go in there have scopes.

B

Yeah, but that that's what we do basically, oh.

A

B

Yeah we we, the thing is that the current activity is what that is the one.

A

B

You which os activity scope enter. You did.

A

B

And the thing is that, if they really they delete that value, uh we don't know uh where it is. So we are basically doing that.

A

B

A

Okay, well, this is the thought.

B

Yeah, I mean it's an api, I it hasn't changed for a long time, and I remember I I did a lot uh propaganda is it?

B

Where is it come on? No.

A

Is it in the sdk.

B

Oh, it's in sdk, okay,.

A

No, that's not it.

B

Internal internal product, no.

A

You know where is it?

A

Oh, maybe propagation in there.

A

You had a propagation in the traces.

B

Activity context manager, who's in open, telemetry, api context, okay,.

B

A

ah Okay, there, it is.

B

B

Yeah we get the current context getting the current, so we have here the current one and- and this is the when we enter, but we have to assign a parent. uh So we we got the current one who can be zero or the other the, but you don't have different levels. You only.

A

B

Yeah yeah, okay, so yeah. This is what we do. We create our activity and just scope enter it's time we get into one and it's complete when we are removing.

A

So you can, you can pass it the os activity, none instead of current when you're creating a new one.

A

But I don't know.

B

Yeah, but the thing is that yeah, the thing is that we are using current, because if it's a child span, you want it to be the side of the other.

A

Yeah also, but whatever.

B

When you, when you remove the contacts you have your parent.

A

B

uh If, if you yeah and the in theory, the first one uh is zero or whatever it is,.

A

Yeah, it can be.

B

From from the user code, and we we can still uh remove hours and leave the user have its current activity, it's a very. It doesn't have many possibilities. Yeah I mean if, if it's breaking this, uh if this value is being resetted, somehow that that's that's, where yeah.

B

A

It's the only way.

B

I found for for having automatic contact handling.

B

The arduino I've used has checked the tracing things that they have for swift, the swift tracing library or something like that. I don't know the exact name, yeah.

A

They are using.

B

The async await stuff and using task so.

A

Oh interesting.

B

So that, but the thing is that you cannot use that, uh except if you write it yourself, I mean you cannot use that from outside uh the cast the the client code. You know what I mean you have to create a task and whatever is inside. That task will get your context.

A

B

It's a task related context, so you cannot set a context to other code. Yeah.

A

B

If it's not taking your task and your things, so it's like very intrusive uh thing to work.

B

But I would say in your in your situation: it should be the probably starting it a bit later. uh I I am because probably the compiler is doing that at the beginning of the app yeah. When it has finished loading, it should be ready, but we yeah, uh I I I will try to check with a ui, with a sweep ui up just to check if it's been somehow uh removed uh during the life of the app or something like that.

A

Well, there's also been the xcode update, so it might be worthwhile trying just trying again and seeing if it changed at all.

B

If it's related yeah, it could be that the new metal compiler fixes that or something like that, uh but yeah, uh but if it's the metal compiler doing it, uh probably it's not related to xcode, except if they change it.

A

B

A

You mentioned that issue and I did put a break point in that location and it does hit that break point when the app is loading, so it could be, it could be related.

B

Okay, yeah, okay yeah. I will I will yeah. I I think that should be the.

B

uh That's really the easiest yeah.

A

I think I mean.

B

If it's presenting it later, uh we cannot do yeah.

A

Yeah, I don't know.

B

How to solve that, because I, I don't think it's uh we can solve it from our side.

B

But yeah, but if that's an issue with a metal compiler personally, possibly is breaking others. People called also.

A

B

A

B

I will I will release a version with this and me I appear whenever it's oh, it's finished and didn't fail with a flaky test again yeah yeah yeah. I should fix that. I tried to remove some of those but yeah. It's a bitter nightmare yeah. That's all right!

B

A

um I was planning on improving the open, telemetry swift documentation. um I was going to add. You know to kind of bring it more in line with what uh the java sdk has like for getting started and stuff like that, we just had some customers who are like. I don't know how to make a trace and oh yeah, okay and um and so.

B

So you are you, so your customers are already using your uh your sdk and creating open telemetry response.

A

Yeah yeah they're trying it out. I don't know if they're using it like they're.

B

Testing it out nice yeah, um so I was.

A

Going to improve the documentation there to help help people out in that regard,.

B

Yeah, I I I I also.

A

B

My customers to create expanse and set attributes to current uh spans, but I wrote like five lines of simple code, but I don't think.

A

B

Really tried that.

A

Yeah, I think that's that's like I mean I pointed them to the um the examples um and I think that's what they ended up using, but they were looking. They were looking for, like docs.

B

B

Okay, yeah uh yeah, I think you know uh vinod was going to produce produce some. You know uh some time ago. He said he was going to work on some uh tutorial or something like that long ago. uh Yeah, but probably he got into other other issues.

A

Yeah, it sounds like it yeah, maybe.

B

I'll ask him.

A

If he has anything hanging around um to speed things up.

B

But I don't, I think, he's now focused more on on his personal assets.

A

B

A

B

Last week, just to say hi, so yeah and told you talking about your peer and your, uh I mean it's really nice to to be able to uh add data for to open telemetry. So we can mix everything there as the central point of of of metrics for for doing everything, yeah.

A

Yeah I can, I can show you what I ended up using that stuff for, if you can, let me I'll share my screen.

B

A

So I took those- and I might eventually add this to um the open, telemetry sdk as well. um These are the app um or metric kit metrics for app uh launch time or like app metrics yeah. So like we have like launch times over here, instagram values um there. I don't know why it's doing this, the chart charting stuff and elastic is kind of silly. Sometimes.

A

um So it's like broken down by like first, you know like launch to first draw or optimize first draw or resume, and so it's like you know, zero to 500 milliseconds.

A

uh You know fi half a second to one second and then so.

B

That's that that's what the apple metrics returns, you from the app.

A

Nice yeah and these are yeah and the histograms and they're broken down by you can see it better in this one, but it's like a daily metrics. So, like you know, on the 14th, you know these are, um I call them crashes, but these are like app exits right. Okay, so they're broken down by like what caused the exit, and so these are all abnormal exits or crashes.

A

So it's like a way to kind of get a value on your app crashing without hooking into the uh yeah.

B

That's right: the top exception handler.

A

Which is kind of cool.

B

Yeah, that's great uh yeah, because apple is providing it just uh for free, so yeah.

A

Yeah yeah, yep and then down here I haven't done all the metrics. These are just a couple that I've added so far, but here um is the responsiveness and app like hang time, so that's broken down into milliseconds as well so like when that ui stutters.

A

B

That's kind of.

A

B

Yeah that that's cool- I don't know if it could be mixed with someone, the things that you can uh check on, runtime and and use it to compare. I don't know if the time that it provides its does it provide uh a fixed time or just uh something like.

A

B

A

The period of the day yeah, okay, yeah, it's like yeah, so these ones are just yeah buckets of of like um yeah, like so like 300 times in the past. So I have it set to three days right now, like 300 times in the past three days, the app has stuttered. You know for.

B

50 milliseconds.

A

Okay and that's across, like all devices that are reporting, which is just mine, because it's a test tab.

B

Yeah, it is it's, it's really powerful. I mean uh yeah if you use that there is like uh really nice, yeah yeah.

A

Yeah, it would be so the the api provides a um rather than a daily report. It also provides incremental updates, as the data becomes available, um and so I might, I might um try that out as well and then that'll be more um accurate information rather than these histograms that are daily histograms, because they're only like yeah, you see like this one was from the 12th and then this one was from the 13th and for some reason the way that it reports it. It's like. Oh that's.

A

I don't know it's just it's a little weird yeah. This.

B

One's from the 14th.

A

Yeah, so it should like take up the whole the whole day, but I don't know whatever. I think I think it just has to do with the way that I'm setting up the charts. So it's probably my fault.

B

A

No, I mean it's.

B

It's nice uh yeah.

A

Really cool so yeah I'll, maybe eventually push those up as a pr to more instrumentation for the sdk for the hotel.

B

Sdk yeah, that can be great, I mean I don't know, I know. Also there are other people doing things with it, but not not providing much code.

A

B

Try to all the instrumentation I doing I am doing in pen telemetry, so the url session instrumentation. I am using that directly from open, telemetry, uh so yeah. So that's how I discovered that it was so slow and try to make it faster, because it's what I use and well, I have to change, for example, the exporter, because I am now using that for exporting many more things than just open, telemetry stuff. uh Currently, so I.

A

Didn't want it to.

B

To I mean make it worse, so uh I am just. I have to duplicate more or less the exporter. No.

A

B

Stuff that it's not open, telemetry related, but I yeah.

A

B

A

Also duplicate the exporter to do some additional stuff, but it's just another. An interesting kind of thing.

A

Yeah that we're gonna remember.

A

No, maybe not maybe I extended it somewhere else. Oh well, yeah.

B

Yeah, I used this for for a lot, but after some changes and we ended up using uh some private endpoints that were not the ones that we could use uh like public apis, yeah.

A

B

Have I have to move out, I mean I didn't want to mix uh those things and or making the exporter much complex.

A

But it can be used.

B

For standard users, if they want just to report uh so yeah.

A

Makes sense for the rest of the.

B

Rest of things that are related to to tracing, I am using directly what's in the package, yeah.

A

B

A

B

A

B

All the stuff that I've.

A

Added I've I've done first in my agent and then like yeah. The the the uh elastic agent is very bare bones, because everything I add to it gets pushed up to open toiletries.

B

That means that your code is more tested directly yeah.

A

B

So you don't have to wait for your customers to uh to say so. Yeah.

B

Yeah I yeah, I will try to uh show you uh what I'm doing other day.

A

Okay, because it's very different.

B

To this uh uh more about instrumenting testing and and yeah, and and I'm doing some some fancy stuff with the with.

B

A

Let's see, let's see.

B

Yeah, I I will try to show you something uh next next week.

A

Oh next week, okay, all right I'll wait.

B

Do you want to see it? Okay, I mean yeah sure I can. I can show you if.

A

You got something.

B

Yeah, I have something. Let me, let me show you.

B

Let me yeah yes, one.

B

A

If you don't have anything right now, that's fine.

B

Yeah, it's a bit it's a bit uh yeah, I mean I have many things here, but no.

A

B

A

Takes a while to get something just ready to demo, you know, like you, have to make sure that it's in a good state because you're always fiddling with stuff. I have the same problem. It's like. I have to leave it if I have a demo tomorrow, it's like okay, like let's stop fiddling with stuff right now,.

B

Yeah, that's true.

B

B

Yeah trying to find something that maybe sticks: okay,.

B

B

There is something like yeah just a bit. uh This is my best thing that how can I serve my.

B

Okay, so this is basically uh you, you have your tests running, that are that, and each of the tests includes uh a lot of information about what happened with the with your test. Has the device where it runs, your ci information get information.

A

B

Commit all the information about language also about your runtime on architecture.

B

And information about the test, also uh the execution order process id the name of the parameters, and everything like that. So you have like um like integration tests, so you, for example, yeah- can have network request, not this one uh yeah. This is.

B

Yeah, like your expanse here uh with network request, where you have all your call stack, for example,.

A

B

uh It's partially symbolicated also, so you more or less can understand your context and.

A

B

The network instrumentation, where you can also show the payload if you want and all the stuff, so you can try to understand why at this phase or something like that? Oh that's.

A

Cool, how are you capturing that um that stack trades? Are you just using an exception.

B

No, I am using the thread local.

A

Oh okay, okay,.

B

A

That can be pretty expensive, but.

B

Yeah interesting, it is expensive, but it's an on test time. I mean yeah.

A

Instrumental so.

B

You so it's not a big deal. Yeah.

A

B

Mean something like that, so basically you you can have all your tests and and see when tests fail and things like that, like uh all my failed tests, these are uh this failed. Okay, nice, I don't know, and somehow it failed right.

A

B

You have your errors and you see that it was an asynchronous way cool awesome. So the idea is that you have your test.

B

Instrumented, always you have organized by commit, uh so you see how your tests are behaving during time and things like that.

A

So cool, that's super cool.

B

And yeah- and it's like you, can track at your test and you can try to guess why a test failed at the ci. That's something that's not usually uh easy, yeah trying to get as much information as possible.

A

That's super awesome.

B

And yeah it has it's what we started doing before data doc acquired us. It was the product we had. That was also based on open, telemetry, uh the beginning list of the suite thing, and we we ended up doing more or less the same uh for data.

B

Yeah and it has some yeah- I also if I have classes I'll, also symbolicate them on device, and things like that that are also cool when you want to know why something fades and things like that, but and everything is open source. So it's on the on my uh yeah, the repo.

A

B

And it has some.

B

Yeah, it has some really interesting tricks.

A

B

I'm always looking for new.

A

Interesting tricks with swift, because it's not you know all my interesting tricks that I know are for objective c. So yeah, that's right! Yeah.

B

You usually yeah at least the the system. uh Libraries are useful, uh objective c, that you can uh track better yeah, yeah, so yeah, and you can treat that a bit. So I so I was thinking another instrumentation to some other things. Apart from the network, yeah.

A

B

Probably uh I will try to work on that, also okay, more or less soon, and also asks uh permission to work on logs for open telemetry.

A

Oh nice, yeah I've been I've been asking in the uh uh the.

B

um What is it the client side yeah the client.

A

Side sig, if anybody wanted to help do logs and no takers, no takers, yeah.

B

That's right, yeah. I asked my my manager to have some time and work on that, but I have to wait after our conference that we have in october.

A

B

I am preparing some stuff uh for that, uh so once that's done, probably my priorities can change and I can take some time for for open telemetry again, at least for solving some of the things that we have not done. But right now I have been full-time working on on some stuff we have to present in october, so, okay, nice cool.

A

All righty, okay, anything.

B

Else uh not from my site, yeah, I don't have anything I will. I will try to release it. Do you want it today tomorrow, no rush.

A

Okay, I've got I've got some stuff that I need to work through. Well, uh I'm actually currently kind of blocked by a stack release for elastic. So there's not I mean there's no rush for me. I think I've got like two weeks until.

B

The sac release I mean releasing, it is, like you know, just creating attack, and everything is just there yeah. So.

A

It's really fast, it doesn't take no.

B

A

B

A

I think tomorrow's fine.

B

Okay, yeah great uh so yeah. I will do that tomorrow morning. My.

A

B

A

All right see you nacho have a good.

B

Weekend, bye, guys bye.