GitLab Monitor:APM Team, 6 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

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

Description

Weekly meeting for the Monitor:APM team

A

A

B

B

B

C

C

We can get started since it's the top of the hour here will give garage a minute to join, but I can start with mine. Just a reminder that next week or not next week, tomorrow is the iteration retrospective. So all the managers have been doing this iteration training, and so this is part of that process.

C

So we would just kind of want to walk through some ideas, a walk through with the team of go through some examples that we've done with either good iteration or successful or ways we could have improved and then see if we can pull out some learnings from that and roll them up.

C

So there's two meetings scheduled for tomorrow and that's just to it accommodate different time zones, so don't need to attend both or anything, but if you can plan or if you can kind of look through some of the work you've done and see, if you can find any examples that you can bring along with to the meeting, that would be very helpful.

C

Okay drive on to you.

A

I'm sorry right a bit delayed all right, oh yeah, so the first issue is what we have this issue to add or authentication to the manual from ETS configuration a little bit of background about this. Currently, the way we are the manual prometheus configuration set up as a project can just connect to Prometheus or tennis instance, using the API jörg, and the assumption there is that these api is publicly accessible, but that's not always the case they could be behind some kind of an authentication.

A

So this issue is about letting the user add more than just the API URL, specifically over the credentials, and this issue also is particularly about just Google's what workflow, because this will help with our dog feeding efforts as most of our media sort. Eros instances are behind Google's IEP, which is their authentication system, so the UX for this is mostly ready. It is just about adding a couple of input fields on the UI.

A

It's mostly a back and fix, obviously, because there's a lot of what handshake that needs to happen, and so, if somebody has bandwidth, please take a look at it. This was originally meant to be done in 13.0, but there's a lot of back-and-forth with your ex and now the designs are ready, and hopefully we can get this done by it is 13.1, and the second topic is also mine. So this is about editing, custom metrics through the chart. So for the chart options there is an option to add to edit a custom metric right now.

A

The way it works is we redirect the user to to the page where they can edit the custom metrics. But the ideal workflow is that the custom metrics for should open as a model, and so this issue is about that is the final iteration and there are some back-end changes that need to be done, because if we have the custom matrix form as a model, we are no longer doing the page, reload or form submit through a page reload, so I think there's some come on some back-end things that need to be done there.

A

So, if somebody has bandwidth, please take a look at it again: that's not higher priority. Their schedule for 13.1 I broke down the front. End related tasks, a little bit of help on the back end would be great.

B

Just one question: last time, I tried the adding custom metrics from the dashboard page. It opened a model for me unless it's already merge recently or something interesting.

A

So is okay, I'm not entirely sure what exactly that is. So this issue is about editing the matrix through the chart options again, I think.

D

A

Referring to adding new metrics through the model, using the button on the top right, oh yeah, yeah,.

C

A

So if you're able to do that, I wonder if the backend is already ready for us to be able to edit the metric as well. I'm, not sure I have to take a look at it. But that's a good point. I'll take a look at it and update on the issue if we still need back and support for that cool thanks.

B

A

C

One more thing I can throw in here too and then, if anyone else has topics, they can feel free to jump in and we had our company-wide retrospective our two ago or an a half ago.

C

One of the things that Christopher wanted to call out was the work and one of the things that was in our retrospective that I pulled over into that company-wide one and then Christopher wanted to highlight was some of the work we did breaking down the breaking down the issue around annotations and I thought that we did a great job on that. So called that out. We're also I also added it to the agenda for the next iteration office hours.

C

So we can get some more feedback to see if there's ways we can improve even further, so I just wanted to call out that that was a good win for our team and something that's you know Christopher wanted to highlight for the company-wide retro as well.

D

Good okay sure, when the next meeting pathetic scuzz I'm not seeing it I, don't.

C

See it either, I ya the agenda for the iteration office hours. Is it just says? Next it doesn't. You know like we do in our agendas, but it doesn't have an actual date, so I'm gonna try to figure out when that is okay. Whenever it happens, this I'll present it there again. Oh.

D

I, probably encouraged, Roger and or Michael I'd to to join that I think it'd be very valuable and a good good time to showcase still work. You've done yeah.

C

And what Christopher mentioned to me, too, is that it's good to kind of highlight in those meetings in that iteration office hours, it's good to kind of highlight some wins, but then there's also always chances for more learning and ways for us to kind of kind of reflect on what we've done, even even on successes, there's probably ways we can keep keep going and keep iterating. So so that's great okay,.

D

C

There other topics that people want to bring up.

C

C

No okay, well I won't waste people's time then so we can have a short meeting today and yeah. Take care and we'll talk to you later. Hi Ron.