GitLab Monitor:APM Team, 20 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Monitor:APM Weekly Meeting - 2020-05-20

Description

Weekly meeting for the Monitor:APM team

A

Okay, so now this is the her data. Monitor APM, weekly meeting dope has the first couple issues here, but he's not here, so I can vocalize them for him. First one is question: do we want to cover the retrospective of 13 Oh in the next meeting?

A

So I? Don't know people have thoughts on that. We talked a little last week about how to use some of the time during this meeting and I. Think covering talking about some of the retrospective issues would be important. I think that'd be a good use of our time, yeah. So I don't know if other people have thoughts on that. I.

B

Think it's a great idea: I think it will give the sense of the follow-up to the retrospective issues, so I think yeah. It's very good idea. I.

A

Think so too, and it's also a good reminder to everyone on this call to use that retrospective issue to add, add topics, things that went well there things that we can improve, that that becomes very helpful. Then we can cover talked about it in this meeting next week and think about if there's some follow-up issues or items that we want to do all right. The next one is, let's see talking about the default dashboard and custom dashboard I, don't know if maybe Clemente you can talk a little bit more about this.

A

You know you've been pretty involved.

C

So there is an issue that I've created talking a little bit about how so I'll share my screen real quick. So this is an issue trying to get some feedback, I believe from the team and what they think. But today, when it looks like when you want to add a metric as a user, if you kind of have this flow, you can either you know, go create a custom, dashboard and the repo- and you know add the specific camel files or you can go to default.

C

Dashboard click add a metric, which is what the custom metrics of blow actuators, maybe even multiple ways to do this, because there's the UI part and then there's the settings part. So recent conversation have been having what dub is more like hey in the future. It's actually quite challenging to support these two flows over a long period of time.

C

You know right now. The custom metrics over here allows you to add alerts. Custom dashboards, don't have alert, support right now. So at some point you know we do want to make both of them have alerts to be. You know same parity, but is there at a certain point this these two seem to be doing the same thing. So why not consolidate these into one flow? Where maybe we store in a custom dashboard?

C

You can use the amal or a modal but kind of pushing users towards this flow, rather than this other flow that stores directly to the database. That's kind of the discussion here, I believe.

C

Yes, so the idea is that you have a way to add it through the yellow file, which is kind of our default thing, that we've been investing a lot into right now, as well as having a modal kind of add metric instead of having that custom metrics be part of the flow. So a long winded way is saying that custom metrics does a lot of the same things in a long term as a kind of our custom dashboard solution, and we want to consider maybe creating a path towards removing the custom metric flow out flow.

C

But that feature in some ways in favor of something that's more robust, so I hope I did this justice, but hopefully that makes sense. Does anyone have any questions about this.

C

Ok, I'll take the science there's no questions. I will reiterate that this is go ahead.

D

Sorry so, in the second image, the proposed roadmap for default slash custom dashboard. If you look at the first flow, it says: go to metric dashboard click on add metric fill the missing information, click Save Changes. So this adds the new metric to the Bimal file. I! Guess yes,.

C

This diagram, but virtually is not the best. But yes, the intention is when you fill in the missing information and save siamo file, so.

D

It's like the custom metric workflow, but instead of saving to database, it saves to the fine yeah.

C

Yes, yes, that is, that is how I see it it could be.

C

There could be something else that I was thinking, but so let's, let's ask that question here, but that's my understanding is we make kind of like how, in its CI llamo, that's kind of the driving factor for CI would be similar to dashboards, but the adding metric modal and that stuff is kind of like another interface abstraction to it and yeah I mean we with there's discussion about how we can better load the yeah mol, dashboard properties into the database, or maybe sync them in some ways to make them more, like faster I.

C

Think that that's also still a good idea, but yeah and I do want to mention that here this. This idea of consolidating is not something we're trying to do like Nix release. It's just you know trying to have those discussions for the few sure.

D

I just want to say I'm. This is a probably a very good change, because maintaining both those paths caused a lot of problems in the past mm-hmm cool.

C

Please comment and share that positive feedback and issue yeah I I, think I, agree. I, think that I, my understanding, I wasn't like super as involved when we added custom metrics but I, think custom metrics was added before we had custom dashboards as kind of a first MVC button. Now we're in this weird loop where were like supporting too close and I, think it's it's costing us a lot. So I I also think that this is.

C

This will make it easier less confusing for users to from a UX standpoint, so yeah cool any other questions for the other people.

C

Cool I wanted to say: I didn't finish typing this, but uh I I wanted to say also congratulations to team for an impressive 13.0. We shipped a whole bunch of things. So good work, everybody a lot of awesome, notable things. You know various variables for dashboard for the input field as well as drop downs and then single chart and dashboard deprecating, a bunch of things. I know that we switched from liquid and installing dashboards.

C

So a lot of a lot of awesome, awesome, wins, I, don't know if somebody else off with the variables for dashboards actually listed as a featured release post item so usually I think every release blog post there's like four or five notable features. So we made it to that list.

C

So good work, everybody very, very proud of the success here cool and then the next thing is one.

A

Thing on that in the retrospective issue, that is linked above here there's a list of all the things that shipped and it's a quite a long list. So it's pretty impressive huh and that's just the list of deliverable labeled things so yeah, it's just a Hey, yeah I, I. Second, that that it was pretty impressive. How much how we accomplished so good job. Everyone well.

C

Done everybody cool and then 360 reviews. Someone asked me about 360 reviews who wanted to share on the weekly call. There's the link about more information. Io de Rochester, though how many reviewers the alder. This is actually from the link, but it's not parsed in the easy way. So there is no like minimum or maximum based on the last time, I did Theresa reviews for number people, but you're trying to shoot for around seven.

C

You want to get get a wide range of people, so you can get different perspectives, but you also don't want like you know, everybody get live because then that's a lot of work for and then you know, there's a law of diminishing returns to when you get to people you might get conflicting feedback things.

C

There is a deadline of May 25th, and that is when I think I think the deadline is May. May 25th, according to the handbook, is when they're sending an amount to people and I. Think then, you cannot add people after they review request has been sent out any other questions for 360 reviews that I can maybe help answer now or even Matt can answer.

C

Okay, all right I guess I'll. Take that as no no question feel free to ask good on slack. If you have more questions on that Michael I, you wanna go for it. Yeah.

B

Thanks so I just want to invite again everyone to show their feedback around month ago. I start the issue with the proposal on to how we organize the code base and how we are going, how it would help to place the features that we shape into the dictum spaces inferred based on the product categories.

B

Little help identified the domain, expertise, I everyone around gitlab and also it will help us to find the parts of code base that we are are going to maintain and I have some time to follow up this milestone and created my request, which describe the change as a first step to introduce it to end before it will go, live or not. Go live depending on a decision. I want to invite everyone to share the feedback.

A

You and it looks like it's primarily for our back-end right.

B

If you have the idea how to extend it for the front-end or if it's could be useful for the front-end I'm more than open to cover the whites wrench, it is from the backends, because I kept more back in expertise, so feel free to extend it.

E

All right thanks, Amy you're up yes, so, rather than deal with small problems, I thought I'd deal with their really large. Would a six thousand word problem actually I have a proposal for one possible way to split apart the prometheus page into multiple pages. What I will want to do here is get feedback from as many of you who are interested as possible fairly quickly because changes flow into this page pretty much on a daily basis. I figured I have a short window after a release where maybe people will leave it alone for long enough.

E

That I can split it apart into about five pages and then go clean them up. If you have suggestions- or you think the the proposed ia hierarchy I've got is a good idea or a terrible idea. I want to know, because it it's important to get that part right at least the the page, the page URLs. Once we have the URLs in place, we can move stuff around if we don't get it right, but the URLs changing them because of slash help.

E

It's a total pain, so I want to get this first part right and get it right as quickly as possible, because I know none of you love working on that page. Yet don't even try so get in touch. Let me know what your thoughts are, because you all have spent a lot longer being annoyed by this page than even I have so, let's make it right.

D

The plan of this way to break down into index panels and variables under matrix / pose that.

E

Was my first idea, I suspect we can get at least two more pages out of it, but I thought: let's just try to land something. First, we can keep splitting afterwards if we find there are more topics that deserve separate pages, just stopping the pain and stopping the bleeding is my first goal here.

B

Yeah, it sounds really cool.

A

C

A

You good any other topics that people would like to bring up today.

A

Okay hearing none, then we can adjourn for the day, so have a good rest of the day and we'll be talking hi. Everyone.