Open Telemetry Uncategorized, 31 May 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2022-05-31 meeting

Description

cncf-opentelemetry meeting-2's Personal Meeting Room

A

A

B

Sweep one more minute to save.

B

We can start on topics on the agenda, so I'll just update what I intend to do for the release. uh Try to find the milestones just one. Second,.

B

However, you should open what exactly okay. This is just once we do the actual release. I need to re-enable the aph combat check for inventory thing, so this is a release milestone which we are targeting to do like today. So I'll do the, I think I'll call it like release candidate one and keep it for one or two days and then make it uh one, two three, uh so this one is done, the prometheus one is not done because the spec is still not.

B

These are actually done or all of the other things are done. So it's like very lightweight on features. It's mostly removing this thing: uh fixing the in-memory exporter, some improvements to the log exporter, so any peers which are not directly related to this one. I I just like temporarily block for two more days, so we can release 1.3 without any description, because the rest of the pr's which are in the pipeline are fairly big. So we want to give it enough big time before we call it step, so that's only update on 1.3.

B

So as soon as we're done with 1.3, I can kick start the 1.4. uh So it's not finally decided whether we'll do it on november 30 or we may do it early. So that's something which we can decide next week, because if you have enough uh payload, we might be able to do a release before november 30th. The this date is because we want to support the new features from dotnet, so we can only stable it stabilize it only by end of november.

B

So, depending on, like whether we have enough payload, we may have a 1.4 like sometime before number 30, followed by 1.5 in that time frame, uh so we'll decide that we can take a look at all the remaining issues and see which one is important and who has the bandwidth to tackle them and based on that will decide. So that's the only update uh in terms of like releases, so uh island, maybe like quickly like. Do you want uh to do this as part of the 1.3?

B

If that's the case, I can just like maybe like wait for you to make a small tick here.

A

uh Yeah, I'm gonna fix that very shortly. I just haven't gotten to it. Okay,.

B

This morning, if that's the case yeah, I can just wait because I think it's a very small thing, so we can just wait for it and once we are done with that, I will do the actual release.

A

Sounds good yeah, I think yeah. I think that would be a good one to get in. um But besides that, I.

B

uh Yeah everything else is fairly big. I think yeah prometheus is anyway not tied to this really. So this one is a bug which fish opened a couple of days back. So this is not a fix for the bug. This is just a test is proving the bug I mean we can merge it. The fix would be like anywhere coming for 1.4, ok, so yeah. This one might require some discussion, so the there is a new package, extensions dot, propagator, which we should be able to create as a core package and release uh straight away.

B

So let me just open that, because this one, as of today, only contains the zipkin which was already stable, so we're just changing the package as well. I will go ahead and release this one, also along with the rest of the things, and then there is a pending pr, which is adding the new uh jaeger propagator, so that can go through the regular cycle. Like one point, four beta one bit adder so we'll have like enough time to validate it before we call it stable um yeah. Most of the things are like fairly big guys.

B

This is fairly big and this is like really big uh yeah, this one we already decided there would be my there might be some making change. uh These are relatively small, uh but we don't want to do that in 1.3, because we just have like one more day left this one. We already have changes requested and this one is waiting for more changes um yeah. So I think that's the only thing which I wanted to discuss.

B

There are any questions or any other topics you want to discuss. We can have them now, otherwise we can end in six minutes.

B

No questions right, so we see again all next week. Now then like just give me a ping like when you're done with that uh push, so I can start the actual release process. Yep.

A

You bet it'll be within the next 15 minutes, I'll play yeah.

B

Sure, oh by the way like one related thing, is like we started moving.

B

Instrumentations to the control group, I think we just did the first one um here. Red is one stack, exchange radius, yeah right here. So uh let's like wait for like a couple of them to be migrated, and then we do the actual release from here.

B

You haven't done a release yet from here right, the new location, uh no, not okay, yeah, let's move like uh at least two or three of them. Also.

A

B

You I didn't move the example code for you know, let's move that also like when, when we move then we'll know like whether there are any other things which are dependent uh yeah. There is already an examples folder here, so maybe we can modify this to show uh reduce example as well like steal, whatever we have on the interpreter, because the main ripper can be like really trim down. Yeah produce a number of examples.

B

So yeah uh like do you have in mind like what would be you moving next like we just did the stack exchange, uh any thoughts on which one you want to move next class start with the sql plan. I think next, maybe yeah so one thing which we discussed like two weeks back or maybe three weeks request we like to keep at least two of them here, so I I wanted to keep sp net core and http client here, maybe grpc, because your pc is built on top of this.

B

So it's like it's like a package, even though they are physically separate package. So we could keep these three here and move everything else to the instrumentation repo and the reason was we would get like some free end-to-end testing coverage by keeping like some instrumentations here we.

A

B

Treat these as a like reference standard for others to follow.

B

It may not be the perfect example, but at least it's it's like so popular in the network that we could choose to keep them in the main trip and yeah in the future. It could be more out, but as of now, let's move everything else and keep in that case, like sql client, also pretty common. uh Maybe uh that would also be a good argument.

B

So there is another good reason why we want to keep sql client, because that can be a good example of how to write the uh write, a proper instrumentation, because this one does not have to deal with any legacy activity or.

A

B

Of like very complicated stuff, maybe if that's the case, let's move the asp.net one, that's it! Okay! We can keep this for here uh and once you do that, like let's do an actual release from the new place and then delete this folder, then only we can call it done. Okay. So let's do that for stack exchange, ready, spinach, spinach, telemetry http module this four ones. Let's keep it here for now and in the future, if you want, we can decide whether we want to move the grpc outside or okay uh yeah. Any.

B

I know like any, like, I think, ellen. You had like some comments like I forgot, like we discussed this like few weeks back, but don't recollect whether there were any open comments.

A

No, I think the plan you just articulated there sounds okay, solid to me.

B

Okay, so can you also do one favor, like maybe create an issue and like the main ripper saying that we are migrating, the instrumentation libraries to the country prepo, and we are choosing to keep uh these four here just to be just because they are helping us with into invalidation of the overall sdk and also to act as a reference implementation?

B

Okay, so at least it's like visible uh somewhere here, because people might be like looking for this in the future and they they would find it's missing. So just a paper trail of what we are doing in terms of finish, that makes sense yeah all right. Everyone. Thank you.

A

B

Just have one hold on go ahead.

A

Quick thing, um I might do a quick pr if, if you agree with this, to change the tag prefix for the log exporter, so that when you do the 140 beta release, the log exporter gets the same version as the other core components. The otlp log experts. That should be.

B

Fine yeah can be an issue yeah. You know. I only wanted to prevent like any major refactoring to get into the 1.3. So that's all you think so it's yeah not in that record, then we can definitely take it. Yes, I plan to do it like, towards the end of the day around five o'clock. So take your time and let me know when you're done or if you need a pr review. Just pin. Yes sounds good thanks. Everyone, bye-bye.

A