Open Telemetry Uncategorized, 22 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2022-07-22 meeting

Description

Instrumentation: Messaging

A

B

Can you hear me.

A

Sorry about that, can you hear me now yeah, I don't know. What's up with my mic yeah, I know I think this is gonna, be it.

B

Oh well, let's get started, I don't know where anyone else is, but we're good enough to do this. Let me share screen.

B

Pablo's gone through recently and done a lot of stuff adding a lot of.

B

Component tags pinging code in there's four, so that helps a lot actually.

B

I don't should probably still add priorities to things we can just guess, which is what we've been doing, but I kind of want to have a larger discussion on if we should be doing that or if we just need a triage label like the component labels, actually the triage label- I don't know, but there's not enough people here to talk about it. So I think we'll just stick with what we. What we've been.

A

A

I think this is a feature request.

A

uh Let's see which one is this.

B

A

I'm not familiar with this, but I think it would depend on if this is an advertised feature. Mm-Hmm.

A

I'm just going to click priority to keep going, make sense.

B

A

A

That's a little hard to say um yeah, I mean that seems like a an error right. um This.

B

A

A

Yeah, I don't know.

B

But it looks like a real bug.

A

Yeah that looks.

A

B

A

Well, if it's a panic and it's after it starts it.

B

A

Pretty serious, I think, probably pube one on this.

B

A

Same traces, metrics for spans processor,.

A

Out of bounds so where's the file get dimensional value in processor, dot, go.

B

um Seems unlikely that that's related 10 months ago.

A

B

I know that there were changes to this processor recently, but not not in that line. 493.

A

So what it said.

A

What's the most recent, oh.

B

This is the this.

A

Is the lowercase version of it, which I think is what I'm actually searching for uh it's yeah.

B

So this is the actual one. So it's actually failing right here um well somewhere around here.

B

Yeah, this seems like it's definitely a bug.

A

B

Did you find something.

A

No, I was just looking at the pile overall to see if there's anything that would um there.

B

Have been changes recently to the that processor, I think there was at least two changes.

B

Three changes.

B

Oh sorry, that's a I don't know. I forgot. We started linking issues sometimes.

B

But I don't think that these caused the problem like this one was seems unrelated to that section. It looks like it was getting upset about some attributes and I'm not up to date on what these other ones are, that one looks probably irrelevant and that that's also irrelevant so yeah, I don't know my guess. Is I've just been in there and they discovered it, but yeah.

A

I mean they shouldn't be panicking.

B

Yeah did they say that uh it was? It was not happening before. Let me ask that.

A

A

I do want to see where is their spam? Metrics processor.

B

I mean maybe like this isn't here. One of these is missing or something I don't know I don't feel like it should panic, though, so.

A

Yeah, I should log in here at worst,.

A

B

And aware of this one there's a big track on this, the higher ones prior to two. So I think we can just hit priority two on.

A

This one and move on.

A

A

This one's got an open pr, so I think mm-hmm, cool.

A

A

B

This is an aws thing.

B

Kind of tempted to ask them if it's on the let's see if.

B

Let's see if there was any changes to that component, that would.

A

Have affected this? No okay, so it's probably still a bug.

B

Even though it's from an older version.

A

Check coders, okay, this.

B

This looks like a nice uh help wanted good first issue.

B

It's just updating one of our workloads.

B

Oh wait: does he close it.

A

Well, it's I.

B

Think there's more to validate.

A

Entries are not allowed, and this says just remember unnecessary ones. It.

B

Removes unnecessary, so I think there's still, we still want to be able to validate yeah. So I don't think the issue is closed. Did he.

A

B

A

Issue was it fixes.

B

He just said related to.

A

Release, that's.

B

Yeah, okay, so yeah, so they want to be able to validate the that all the entries and the corners are valid and not in the allow list. Yeah, that's good! I think that's a good one, and I wasn't thinking about how wanted on any of these prior issues, but I don't think I would be able to say a lot of these felt like they needed an investigation. They all seemed like bugs so probably leave them as they are.

B

Man we had a lot of- I guess, there's only one page of new stuff. It's not that bad all right, uh individual log records since complete resource loans, which consist of scope logs, that's true,.

B

I mean that's: how open telemetry works.

B

I don't I mean I guess the exporter can do anything at once, um so the next border could be changed like the kafka. Exporter could be changed to better stoop koska's knees. It doesn't have to output the records in the way that open telemetry relates everything together. So I think that makes sense.

B

I'm not I'm priority needed, because this isn't a bug and I don't know how much they care about it. The code owners but diff is definitely an enhancement, so I think pablo got those right cool.

B

I think this is going to be the same thing.

B

Someone responded but not the code owner, so I think this is the same thing.

A

Trix transform processor.

B

Aggregate histograms.

B

Dimitri's all alone on this one. This is a feature request. I think I don't well. I don't know if it can do this already hold on.

B

Using prometheus distributor, scrape, histogram, okay and what's happening and after that export to the prometheus using okay, just wait to see one histogram with metrics aggregated, I'm not going to compare. uh What did you see? I saw one for one histogram, but the values are wrong. Okay. So it's a bug.

A

Probably yeah, oh, it is.

B

A

Bug, um based on the the title um hard to see more about it, cool.

A

It is transport processor,.

B

I'm pretty sure this is like a question.

A

uh uh Yeah, that's kind of what it seemed like when I read it.

A

um Where are we down here.

A

B

Since this is another ci one, we can put help wanted.

A

Issue on this sure.

A

B

I don't know why this is in this repo, the hotel exporter's, not in this repo.

A

I'm not following this.

B

Multi-Tenancy using hp headers with the current implementation of the hotel export, we need to create an exporter per tenant yeah. That seems right because you can't well, you could set the yeah. No, you can't change that dynamically yep.

A

uh Apparently, okay, so apparently other exporters have some similar functionality, but.

B

Right, let's take.

A

A look he's looking at the otlp exporter, then it's not gonna, be the right spot.

B

Yeah, I think I'll transfer it. I might not have permission to transfer them. I had to get one of them. People that's in both.

A

Let's see if I can transfer this over there now.

B

A

One of these people.

A

A

Anthony pablo andressi.

A

B

I am now going to make sure that the tlp exporter is 100 in here. Still, yes, okay, they're, both in there good.

A

This is a question.

B

Yeah, I think so too, it might turn into a bug, but.

A

Yeah it's hard to say I don't yeah. I definitely don't have the the context necessary to.

B

There have been some questions that have been brought up about the host metrics receiver in the past, the underlying scrapers, like we use a ghost scraper and it actually was getting it like, generates one of the metrics in like a strange way where it breaks the semantic convention, where, like all the metrics, can't sum up to 100 or something like that. uh But I don't ever remember what happened to that issue. I think it's still open this one might be similar.

A

uh Yeah, it does seem that this seems very similar to that uh it sounds like there's a the units, don't work, how you'd expect well the unit.

B

A

Yeah so so yeah I'll just add a question on that ping.

B

A

So yeah cool all right.

B

Question priority that one we're going to move we're down here at support for logs, hey, that's a nice feature, add.

B

No one's responded yet, but what's this.

A

B

Hours ago,.

A

Okay, I see so it says, link to tracking issue, but not fixes, so I think it yes.

B

I think we can close this.

A

B

Oh here, here's the link thing right here: okay,.

B

B

Oh this one uh yeah this one's getting annoying, I think someone's working on it. uh Oh did they fix it?

B

Oh no he's skipping it yeah, just skipping it. Okay, so very cool this one's pretty annoying.

B

Well, now that it's skipped, actually, we can keep it a little lower.

B

Let's see, I won lit fish. This is the one below cosmic build failures.

B

So this was uh yeah yeah. We we updated this package, the the action, the github action I think, or whatever it's actually doing, the link checking. There was like a new error code that now is like breaking a bunch of stuff, so it's disabled for now, but I think we wanted to add it back. So I wanted any sense.

B

I don't know I mean this is probably okay for well.

B

I'm not going to put help on it on this one because it sounds security related or sorry, good, first issue, because it sounds related to security.

A

B

But otherwise, I think we're good on that. Almost through the page, four minutes.

A

B

Previous group, by prometheus remote right.

B

I mean that feels like a pretty good explanation of a bug. I think he understands what's happening.

B

Yeah seems like a bug feels like they have a good understanding, so hopefully uh I think it's anthony. I don't know why didn't it's ping ah because he did the wrong label all right hold on. Let's do.

A

Processor forward slash prometheus.

B

Oh sorry, not processor, receiver,.

B

I'm gonna throw all three on here. I think, because I seem it seems like it's a relationship of all of them.

A

And slash yes, remote right: there we go.

B

That'll paint a lot of people.

B

Okay, tester failing on windows with a dash race check. Oh it's dimitri.

B

huh I didn't ping anyone.

B

B

Okay, that's why uh the tag.

B

No, no, that's fine. It should be export yeah yeah because it gets appended with the word exported later. I don't know I might have to open a bug if this doesn't ping. Oh there, it goes.

A

B

Maybe this was before um in the last week we did fix something I think I don't know. Maybe I wonder if it doesn't work, if you add two at the same time,.

B

We'll have to I'll have to test that later, I think, did the ones that I've just set work.

A

That's hard to yeah. They.

B

A

Works like it yeah.

A

B

A

When were the code owners updated that.

B

Good point: that's a great idea.

A

I mean it's unlikely, but.

B

Well, actually, there was a lot of code owner updates recently.

B

Four days ago, so.

A

Yeah, okay, good.

B

Good good good, yeah, good thinking.

B

All right, I think we got the whole first page done. Oh wait! I didn't put a priority on this.

B

Did we get the whole first page done.

A

uh Whole first page, oh.

B

A

Gonna, do this last one real fast.

B

Oh there's already people discussing it, I think I'll, just let them discuss it.

B

Okay, cool all right, thanks for helping out today, all right, see ya, see you next week.