Hello, my name is William Chia I am a product manager at KITT lab in the monitor, Health Group, and this is a kick-off video for the 12.9 release of get lab. These are the features that we've prioritized for 12.9. Let's take a look. The first is to be able to filter errors by error status. This is a nice capability that is very similar to other parts of filtering and get lab and lets you get to the issues you need to more quickly.

What's exciting about this feature, shipping is that the air tracking category will move from minimum to viable with the delivery of this feature.

Next up is the ability to collapse and expand charts. This is nice because you can see more of the issue or see all of the charts depending on if you want them to be expanded or collapsed, we're also shipping the ability to automatically embed metrics for all get lab configured alerts today when you get an alert and it creates an incident, you have to manually add the chart to that incident issue, but with this feature, the chart will automatically be added for you. We're also very excited to move the alerting feature in to get LabCorp.

This is part of our stewardship model. We are, we really love our open core community and, as part of our Christmas gift, we wanted to move the three pillars of observability into court and with 12.9 we're moving, alerting we're very excited about that.

Next, up is a new set of capabilities for gitlab called the status page that allows you to have a public page to share information about incidents. We've broken this up into a few different iterations within the same release that we were prioritizing the same release and I'll walk you through them. The first step is the description from an incident, will get added to a public status. Page it'll be text only in the next iteration. We will also show images that are in the status page description, I'm.

Sorry, in the incident description on the status page in the next iteration, we will put that on a CDN status pages, ten, a lot of traffic, especially if there's an outage, so we want that to be scalable next up. We will also have the ability to post comments in an incident issue. You will be able to denote whether a comment is public or private. If it's private, it just stays on the incident issue. It's a public comment. It will also get posted out to the status page, so you can communicate ongoing updates during incident.

Finally, we want to have an aggregate list of incidents, so we'll have a single page that will show you a list of your most recent incidents. This allows you to have some transparency with your users and build trust in your brand. We're very excited about these features. Coming in the next release or prioritized for the next release. We would love your contribution, so the links to all of it is issues will be in the description of this YouTube video.

Please do comment and collaborate with us, we're so excited that you use gitlab and thank you very much.