A little bit about the common language of SLO that helps bridge the gap between business and engineering teams. We’re also going to talk a little bit about how we selected the correct service level indicators to arrive at the service level objectives, which is what SLO stands for and how they managed to get guidance from Liz Fong-Jones who started them out helping them along in their journey. We’re going to cover why Clover Health wanted observability in the first place, why they wanted Honeycomb specifically, and how they’re using SLOs. So Josh has a lot of really special contexts on using this new initiative that’s coming out of Honeycomb and I’m very excited about what we’re going to cover. And what we’re going to talk about today is the use case of SLOs with Clover Health. Hello, I’m Josh Hull, I’m the site reliability engineering lead at Clover Health and I help keep the site reliable. I help customers get started and do all sorts of variety of things in a startup and I’ll let Josh introduce himself here. So a little bit about us, myself over on the right, I’m Nathan LeClaire. So tune in for that and we’ll have some details about that at the end of the presentation here. So hopefully you tuned in for part one in the series.
And especially the success that they’ve had with SLOs.
So what we’re going to look at today is a bit of a story of where Josh and Clover Health come from, why they landed on observability and where they’re going to go in the future.
#Build io screencast series#
Josh Hull :Īnd this webcast is part two of a three-part series on using SLOs. I have a special guest, Josh Hull from Clover Health. So welcome everyone to Production SLOs Success Defined, a three-part webcast series from Honeycomb.io, the one and only true observability tool to debug production and high resolution.
0 kommentar(er)
