Open Telemetry Uncategorized, 20 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2022-07-20 meeting

Description

cncf-opentelemetry meeting-2's Personal Meeting Room

A

B

B

Hello good morning.

C

D

D

B

B

Are there any agenda items.

B

I think, uh since bryce uh since you're back I'd like to point out that we have had extensive discussions on an api for creating events using the logs data model,.

B

And there is currently a pr against the spec repo for that. So when you get the chance, could you review that from ios perspective.

A

Yeah I'll try to get that in this week.

B

Are there any other topics? I think.

C

Santosh, oh, this is let me turn on my video hey. This is trivikram, uh I'm from aws estigas and tools. So we have a small team will be experimenting with open, telemetry instrumentation in aws sdks over next week in and we are aiming to do it in java.net, javascript go and python.

C

So I just wanted to know what is the status there like, but then it's a very less priority, so discuss your things first and then I'll call out.

B

um But one clarification: this group only deals with client-side telemetry, the browser side and the mobile applications, monitoring.

C

Okay, so browser side is includes javascript, right, yeah yeah. So then let me change the agenda, make it specific to javascript, but I'll come back to that. Let just discuss your important stuff. First, okay,.

B

I I don't see anything else on the agenda, so unless I just want to bring up anything.

B

Yeah we could talk about your topic.

C

Okay, uh so you mentioned this meeting is about browser and mobile apps right.

B

C

B

See the the client-side telemetry the what many of the vendors call ram really.

A

B

D

B

Topics concerning.

C

Okay, okay, and this only about specification, also implementation.

B

Well, um it's supposed to be both, but um we have identified several gaps with respect to the specification itself, so we have been working on making changes to the spec to allow for, let's say, recording, standalone events, because currently uh the open telemetry only supports uh spans, um but there are going to be events which are standalone. Events which could occur outside of you know spans right. So, in a browser you know you could there could be errors even when you're not actually making any api calls right same with mobile applications.

B

So there is currently no way to represent. You know those situations, so we have introduced, or rather we are working on introducing uh an events api so that we could record those events.

B

So that's one and there is ongoing work with respect to modeling sessions. There is we have identified that there is no um good way to represent sessions. Currently um the session id is, you know we will have to pass in every signal. uh We wanted some common way to represent the session id in in the payload, but you know we haven't been able to uh find a good place for it.

B

One option was to put in the resource, but you know it doesn't allow the session ids to change if we put that in the resource, because these choices are supposed to be mutable.

B

There is an ongoing debate about that. Okay um and then. Lastly, I think there is another topic that nav is following up to enable nested attributes.

B

uh So currently the attributes only support primitive data types and arrays, but there are use cases where we feel it will be good to even have support for maps.

B

As attribute values, so that's.

A

B

Something that we are trying to.

B

You know get a change in this work.

C

Okay, so my question would be specific to uh implementation, then so I am maintainer of aws city of javascript and we have single npm module which supports both node and browsers.

C

So how is actually I can find these answers from the source code, so I don't want to waste your time. Yeah.

B

I'm not too familiar with it. There might be others who might be able to answer the question. Okay, but yeah feel free to post it on slack. Okay, there is a channel called client-side telemetry, uh okay, that question there or even the hotel js. I think many of us here are on hotels.

C

A

Is as part of the the rum is we're going to be defining events um so actually come out with a so as part of the events api, we're going to say well, these are the standard type of events that uh hotel will support, and this is what it will look like, so that, regardless which vendor a customer uses the event still looks the same.

A

um And as a part of your question, I'm actually the um the maintainer of the application insights for microsoft, so uh very familiar with the website of things um and you'll find the hotel js currently is extremely heavily geared towards node.

A

So I've spun up a a sandbox which I'm in the process of merging the js and the api repos into so we've got history uh and the sandbox is actually called like sandbox web sdks.

A

I think it was its primary purpose is to explore minification and what what can do and should we uh have to to make it. So. This thing works in web nicely because it's um huge, if you're, trying to take the load stuff and drag it in today, which you'll no doubt find out.

C

Good uh thanks, neil I'll, add this the summary under my notes.

C

Well, I don't have any question just follow up with what questions has.

D

um Yeah, hey, I uh I just kind of I've been following along for for a while, and I'm super interested in the space. um Something we're doing at honeycomb right now is also thinking a lot about these questions like what is the session and how does tracing work um like in clients. So I feel like there's a lot of overlap, and I was just wondering like what is I'm I'm just wondering like.

D

What's the best place, I can like jump in and and help out um as someone who's kind of new to to helping out with open telemetry stuff.

B

B

I I think a good place would be to review uh the ongoing uh topics. uh There are pr's, uh there are tips, you know. So if you could review and provide your comments, I think that would be uh could help.

B

I'll add them to the, I think. If you could go through the agenda document, you will find them. Okay, perfectly in the past meeting notes um but yeah. I think, based on that, you will know where things stand and then and then you can see.

B

Now did you have any ideas um on this.

A

um Yeah, it's probably a case of you- should also be going to the or coming along to the open, uh the js sig, which is directly after this one, um getting a feel for. What's there uh there's like a like, while we have the the sandbox or we will have the sandbox functional shortly, the the js and the the js api repos are the masters, so I think I'm spending a lot of time creating scripts to sync from them.

A

um So anything we do in the sandbox will actually push back to those master repos and then sync them back around again. So it's not like the sandbox is going to be the place where express where um uh we make major code changes and then expect to go to prod the sandbox is, will not be prod supported.

A

um So I know martin who's, not here today, uh is creating some experimental stuff for the logs and the events api. um So most of the stuff in the js is browser. Sorry, a node focused, um but it's you know the plane is to have the bulk of the code there so um yeah reviewing that.

A

Looking at the examples, helping, maybe even creating more examples, there are there's a shortage of examples over there um yeah it's really yeah, and then I sent us looking at the o-tips and the specs and finding the gaps and then helping kill them.

D

Yeah, um I have a very specific question, but I'm not sure if it's like the right place to ask, um so maybe I'll ask it, and then you tell me if this is like more. I should like open an issue or something so one thing while playing around with open telemetry.js in the browser is the async hooks context. Manager is very node specific, but I feel like it's like a very important piece for like linking traces together.

D

um Are there any plans or discussions about making that browser and making that, like friendly to the browser.

A

I don't think there's been any specific discussions but yeah. That's it's a problem.

D

A

Sounds good, so yeah you can raise an issue, um I don't know who it'll get allocated to we'll probably play with it in the sandbox and then push it back out, but um yeah that the the the context packages, because there's three of them are three of the packages that I did originally trial uh in my sandbox api, which I'll drop some links in for the pr's that I've that I've got that hasn't merged into there.

A

Yet and it's problematic it's the other issue which you'll probably hit is the global context basis of the js api. So if you want to have a web page with more than one component that has that is, and each of those components have their own versions of the api, that's extremely problematic.

A

um That's also something I'm going to try and address in the sandbox so that you can have component a will have its own copy effectively in its own closure of the of the system, and it won't affect the component b.

D

Got it okay, thank you.

B

uh I added a link to the project poll um in the agenda document, so you could, you could go it. Has a bunch of tickets were working on so you could go through that.

B

Does anyone else have many topics.

C

uh I added notes from what centos responded. Can you folks update the links like event session or complex type, attributes or sandbox.

C

Oh yeah, actually it's been updated below thanks nick name.

A

um So yeah, so I think I've just dropped some links in there, so the main sandbox you'll, find is still empty. The working fork is effective. The merging fork that I'm working on um so that gets the two, the js and the js api and dumps it into a auto, merge, folder and the working structure is ultimately where I'm heading, so that was the working structure was my initial creation, which was a complete just copy of everything.

A

So there is no history. So when I approach daniel who's, the one of the maintainers on um js, he said it was uh unreviewable, which is why I'm spending so much time trying to get all the history over. So the the working structure is ultimately where I'm going uh in terms of the definition.

A

um I think I also have some actually let me put my script in there as well.

A

Here so this is the merging script um and it contains some. If you look in the read me of that, the basic layout of what I'm planning for the scripts but effectively there's going to be multiple branches, um there's going to be the staging branch, the main branch will just be in theory, everything merged and then we'll create sub-branches off that to go and explore different things with different people.

A

So we can all collaborate and then anything we find will push sprs back to the main repos. um One of the major explorations we're looking at here is: is it going to be feasible to continue having the single js and js api repos uh for both node and web?

A

um So that will be another branch that we'll create it may not be, but we're going to explore and try and see what we can do.

C

Just sad question: is there anyone from amazon or aws already working on this.

A

From the sandbox no.

C

Yeah in hotel, js.

A

uh Yes, we, there are a few people from aws in the attend the js meeting. I believe.

C

Okay, I'll attend that it's 9 a.m. Right, when is this yeah thanks.

B

Okay, I added some links.

C

B

Okay, if there are no other topics, we can use.

C

A

Thanks everyone, here's all.

A

A