 All right, I show eight o'clock and folks hear me. Thumbs up, yes, no, maybe so. Cool, thank you. So welcome to the first support group conversation of one of many previous FGUs. Got a few slides to go through. We're going to do a tag team sort of an approach here. I'll introduce some of the agenda in the first slide, and then we'll break into various sections and move on forward. So as from a gender perspective, who's new? We got some self-managed and get lab haps. And then Tom A is going to give us an update on knowledge sharing progress. And then just a quick slide on Q3 and Q4 OKRs. So very excited. We've got a new support APEC manager starting November 12. So he's actually engaged already, and we're trying to get him some things to do before he even gets his first Mac. So we'll be welcoming him in a few weeks. And since our last meeting, a lot of new talent to the team across the globe listed them there. Hopefully we're all able to hear their introductions on the first Tuesdays. And if you haven't reached out and had a coffee chat with any of them, please do so. They've all started to make a big impact on the support team. So a lot of great talent had it there. So thanks to recruiting and all involved. A lot of folks on the support team doing interviews, the exec team for sponsoring offers, and et cetera. So thank you all. It was a very busy quarter in recruiting. From self-managed, Lee or Jan? Hi, everyone. You get me for three slides today. I will let Tom know when to progress. I wanted to just highlight a couple of things around self-managed right now. We're really focusing on diving into Prometheus. We need that. We need to leverage this. We learned that from a customer experience. We had a huge outage with a large customer based in Amia. And it took us four days to get through that. Prometheus was a huge help. And now we are evangelizing that like crazy. We really want that involved for any large distributed deployment. We've seen the light. The other big thing that I want to highlight, Kubernetes is still challenging. I want to give a shout out to Daniel, who's on this call, and other Kubernetes team members who have been helping support. It's been really helpful. So support needs support. Thank you. But Kubernetes still proves to be one of our bigger challenges as customers find those edges really fast around auto DevOps and Kubernetes-based deployments. So expect more from support there. And then lastly, we are sending support delegates out into the world in every way, shape, and form, trying to make sure that we are paying attention. So if you see someone from support asking to join a meeting or asking for links to something or clarity, we're just trying to make sure we understand what's happening and that we're building the right bridges. Tom, next one. One of the real cool things that we've been focusing on on the self-managed side has been performance. Performance engineering. We want to take GitLab to the next level. And we think that it's our responsibility to help deliver performance as a feature to customers. Making sure GitLab is fast. And working and helping with customers means that we get to see GitLab in the wild. This is just a quick little graph. We were playing around with a tool called Ruby Spy by Julia Evans. Shout out to her. Great tool. We're learning how to use these tools to trace and better manage the application as a whole. So really excited there. And on this slide, I'll update it afterwards. Will Chandler from our team wrote an S-Trace parser to help us move and get data out of S-Trace faster. So that's really awesome as well. So we are trying to drive towards more data-driven decisions and make it easier for us to see how GitLab works every piece all the way down to the system level. Awesome. Tom C, last one for me coming up here, if you would be so kind enough to change. I'm known for charts and graphs. And yesterday was my GitLab two-year anniversary. So I wanted to take this premium SLA graph and go two years. The bar at the bottom, that's two years of premium SLA. We still have not figured out the secret sauce. I'm sad to say. This is one of the biggest challenges we've had. There's still fluctuation. There's still ebbs and flows. But volatility has absolutely been reduced. We're doing a great job. Hires are proving to make an impact. And just seeing this chart over the last two years gives me hope that we're on the right track. But it is still one of our biggest challenges. So still diving in there. If you have thoughts, ideas, things you want to talk about, you can always find me. And we'll go from there. So I'm going to pass it over to Lyle. I saw a question in chat, but I'll save it till the end. On the .com side, we're full. We have all the agents that we plan to have. And that is fantastic. I don't know if there's very many places in GitLab where we're actually not hiring. So that's cool. Even better, the number of tickets we're getting to the size of our team is also good. We're feeling comfortable. But we're not quite 100% on our SLAs. And that's because we're focusing on learning to handle complex issues. So .com agents are quickly becoming much more developer focused. The tickets we're getting are harder CI questions and GitLab just moves fast. And our customers are really hungry. So just an illustrative example is our first ticket on the Maven Repositories feature was a week before the feature was officially launched. So that means that we have to know about things before we even know about things, which is cool. It's a cool problem to have. And that's sort of Lee alluded to building those bridges. That's part of the reason why we want to build those bridges is so that we can make sure that we're providing great support even before we release features. Another thing that we've noticed a lot is upgrades and renewals. People want to give us money. And that is a great thing. We're really happy that we're seeing lots of upgrades renewals request across the board into the right place and into the support queue. So we're really glad to have Kyla and Willis handling these. Yeah, so we've just kind of been, yeah. Sorry. I also wanted to mention that Git host is still a thing. It's still around. Customers are slowly migrating off. Many are moving over to GitLab host. And so we are having some go to .com as well, John Woods. So if you click on that link, there's sort of an informal partnership that everyone set up. And a lot of times the reason that they move is because they have requirements for why they, where data can be stored. So we have some European customers for the debt that has to reside in Europe. So .com is just not viable. But we've also had a lot of issues with Git host as sort of like there's less support there and the team isn't as big. We've had issues with backups and upgrades, certificates, backups again. So we're looking forward to June definitely. I think that's it for me and I believe Tom A is next. Hi, everyone. I'm the second Tom in the support world. So for people who don't know me, I look after the support team in EMEA. So there are three of us, Lee Lyall and me at the moment and soon the new person in APAC. One of the things that I'm looking at this quarter is how support can share the knowledge we have. Support engineers, support agents, answering tickets in Zendesk, giving customers solutions. A lot of, most of that is private to the customer and it disappears into Zendesk, which is one of the few places in GitLab where information is hidden away. So wherever possible, we want to make that knowledge public. If a support engineer answers a question twice or three times, we shouldn't need to do that again. We should make it public and make it easy for a customer to find that information and that'll help us scale, helps customers self-serve, keeps them happier and saves us having to be like machines and repeat ourselves. We can actually dig into new exciting stuff. So I'm exploring this at the moment. Nothing active yet, nothing decided, but we are hoping to make progress on it very soon. There are two parts to the project. One is to find the place for us to publish stuff, which we have some ideas on. I've been talking to some other teams about how to do this. And the other part is how to help customers and us get Labr's search for this information. So there are some parallel efforts with some other teams, the docs team, Handbook, also looking for improved search solutions. So we're dovetailing with them to get a great search solution for when customers, for us, when customers are submitting a ticket, that they will be prompted and suggested solution, likely solutions based on the knowledge we've shared. So those two things, having definitely planning to have those up and running as soon as possible, certainly within Q4. And then after that, we want to be able to measure the success of this knowledge sharing. And there's various ways you can do this. Zendesk have some great research on this. The TLDR of it is really measuring how many people are actually using your knowledge base compared to the number of customers submitting tickets. And ideally, you want to be growing as a company, having more and more customers, but you don't want to constantly be linearly increasing the number of tickets that support agents have to deal with. So we will use some metrics to measure the success of that initiative. And there's a linked issue there, if anybody wants to comment or join in with that as we explore that and progress it. Thanks, Tom. Thanks, Lee. Thanks a lot. And from a wrap perspective, we've got the links there for our Q3 Retro, which includes the Good Bad Try, I think the latest Clint Eastwood movie. And then Q4, OKR's listed the link there as well. A lot of the Q4 was, a lot of the Q4 OKR's were referenced in this presentation around knowledge sharing and some of the process improvements, but also performance metrics, holding ourselves accountable to responsiveness to the customers. So that's it. Going into conversation mode. Let me look at the chat. Any last questions or conversations or quotes? Fun facts. So question from Reb on what is the value component? Yeah, we answered that a little bit lower. Reb's talking about in the graph that I had and the value component was percent of premium SLA achieved for that day. Excellent. Lyle, there's a couple of questions on Get Host. You wanna, what can sales help and why folks moving from Get Host to Get Host, Get Lab Host instead of .com? I think you probably addressed that in the deck, but any other comment? How sales can help Lee also address. So I mean, migrating into .com sooner is always great or migrating to self-hosted also great. So yeah, at least reach out and support managers on Slack and we can continue the conversation there, but essentially just the sooner you move, the sooner the less work I have to do on Get Host. Essentially. Always a key element. Yeah, and to just echo on that, if you are an account manager, account exec and you have Get Host customers, yeah, just feel free to jump in to support managers and we can always talk about your specific customers and try and make a plan. We want to do that. We want to help your customers explicitly yours, whoever you are out there. We wanna help your customers. Let's get them going and get them happy. Thanks Nadia for the call out there and referrals and for our hiring in APAC. We're eager to get some assistance out there for our new manager. Hopefully he will bring some references as well. Anything else? Speak now or forever old your Thursday. Okay, I'm not gonna verbalize it, but I'll go to five. I like this technique, Tom. Thank you everybody. Lee, have fun at the conference. Everybody have a great Thursday. What's left of it for the EMEA folks?