Open Telemetry Spec SIG, 27 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2020-08-27 OTel Errors Working Group meeting

Description

No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).

A

A

Hey matt howdy, you talking to you and me today.

B

Looking like it's just us um so yeah, I didn't have much of an agenda to begin with other than um I was maybe gonna give an update as to where things stand.

B

um I don't know is: is that useful, sound.

A

Working for you a little problem with my sound, I just didn't hear what you just done. Oh.

B

Okay, yeah, I was gonna, say yeah, it is probably just us like. I didn't have like a really big agenda. For today um I was just gonna. Give kind of a status update of where things kind of currently are.

B

Okay, so go for it.

A

Yeah I was looking for the the uh vr that you have open for it, so I could go through it and make sure I need some good comments for you, but I think what we talked about last week, I'm on board, with what we're doing what you've got to agree with cool.

B

um Yeah, I guess maybe that's the main update is that um let's see here.

B

Yeah is that I have opened a pr and, of course the zoom money was always in the way um yeah. So I opened this error hint pr, as, as we kind of discussed last time, there's been a lot of good, healthy discussion on it. I think you know the the main issue is this: guy christian has opened another pr that um modifies the same the same api to allow for additional attributes, which I think is a good idea, but it's kind of causing a little bit of a a dependency order problem with these vrs.

B

I think I think, because his has way more approvers than mine. He was hoping that his would merge first and then I would pick up his changes. So I think a lot of this is because he has requested changes and I think he's not going to remove that until his pr move merges. So I feel like this thing is effectively blocked on um that other work, um so I will probably see ping some people and see what we can do about trying to merge um christian's pr.

B

So I can pick up the changes so um so we can at least get that conflict out of the way.

A

Yeah that this was the information I was looking for earlier I'll turn up on the pr I can go through them and just read make sure I truly understand everything's going on and then one thing I'll tell you about, because this is my first week, I'm actually starting to deep dive into open termity. Since I've been joining the meetings, we finally have a research fight where we can spend time and actually get deep in this. So that's the point which.

B

Yeah, it's I mean it's a good time to have some time to work on open, telemetry. There's, there's a lot happening right now, so.

A

What can I do to help you with it? Is that anything I can help you with.

B

um With this in particular, I think it's um I feel like it's in a pretty good state. I feel like the main thing is just um incorporating the changes from this other pr that has yet to merge. So.

A

A

Is it just because the signature, the api is a little different between the two, what we're intending to propose and what he exposed.

B

Basically, we're both adding a new parameter to the same api, so.

B

Basically, there's a, I guess you can probably look at this really quickly, but.

B

We're both adding a new parameter to the same api.

B

um I guess he got rid of the examples in his pr would.

A

You like to add this back to it.

A

B

Been removed, yeah, so basically um the spec as it currently stands is there's a record exception api it can, it can take an exception and then it will kind of unfold, those into the proper semantic conventions and um basically, for an exception.

B

You know you will have like exception dot type exception dot um that message exception, dot stack traced.

B

So this is kind of like the really simple version of this api method, where you would pass all those in individually, but it's like, if you actually have an exception, object like there's, there's no reason that you should have to drill down into the exception just just pass it in and like have it record the right attributes for you.

B

But basically, in this guy's pr, this is just a wrapper around add event, because it's recording an exception um as an event on this fan.

B

So um in case you want to add, like some additional attributes to your event, that's kind of what he's adding in this pr is that.

B

Yeah that should allow some additional.

A

Audio went out completely for a moment. It messes up on the game that your internet connection is unstable, but it was in the zoom window.

B

Okay, so that might be my internet today, I'm not really sure, but basically um all right. Let's see if I can summarize this we're both changing record exception right now like this is what exists is record exception with an exception, I'm proposing that we have this in this pr exception and error hint, and that third par is basically adding in this additional attributes.

B

If that makes sense,.

A

Yeah I like that. I think I didn't need to control whether to actually flip that amp flag or not.

B

Yeah, so I guess the good.

A

I mean you basically what you say here is you're hinting whether this is record reception.

A

Sometimes I'm saying it wrong whether this exception you're about to record is something you think it's an error or not that's from a programming standpoint, and so yes, we can do something different in api.

A

B

Yeah, exactly um and- and I think that's pretty accurate- this is like the best. The best you can do is the programmer can give their very expert opinion on um on the situation, um but there are there are things downstream that can um decide to honor or ignore that um that hint.

B

But yeah, that's that's! Basically, where things stand so.

B

I don't know that I had too much more for this meeting.

A

Yeah, that's probably basically waiting to see what more people have to say about that. You haven't been fully funded.

B

Yeah, so I don't know if there's anything else, that we should talk about or if maybe we should end this, I know we'll be at we'll, probably get the ruby sig before long.

A

Yeah it'd be nice to send you a little bit more time because I'm going through the prs would we be doing I'm trying to depend on what what to work on and we'll talk about intake meetings? I'm gonna ask some questions about it. What what or some quality? Where can I help and you thinking about that? For the reason you can talk about.

A

If you want, but you know what we're trying to do is we can figure out the gap between what open terminology ga targeter and where ruby stands in relation trying to understand that director for ourselves, and especially me, I'm going to understand that so I can see where I can help get us to ga in the movie, though, that's my goal.

B

Okay, yeah. That sounds good. I think, there's a lot of things that could be done and we should probably um prioritize our backlog now and get like a required 4ga label over there. I don't know if we.

A

Have that label.

B

Yet but I think um yeah, I think we can talk about that at the next meeting, but I think that would be a good idea for us to have.

A

B

All right, yeah see you at the next.

B

B