Welcome to day one of our very first Launch Week! In the upcoming days, we’ll release new features every day. We’ll share new alerting capabilities, unlock the power of Playwright, and will talk about new ways to control and write your Browser checks. It’ll be a nice feature and improvements mix, trust me! To kick things off, let’s have a look at what’s new in the world of monitoring and alerting.
The Checkly development team is continually improving our platform and user experience, and we’re excited to unveil some new features that we’ve been working on during our first ever Checkly Launch Week. From October 11th through 14th, we’ll be announcing and discussing our latest innovations, new features, functionality, and capabilities for users every single day of the week.
The demand for continuous innovation and faster delivery requires a fresh approach to monitoring modern apps and APIs. As development environments grow increasingly dynamic and complex, monitoring performance through a platform that is fully programmable, handles app and API-testing, is optimized for developers, and integrates with existing tools and workflows becomes increasingly critical.
Let’s admit it: end-to-end testing is a technical challenge. How do you make features testable? What testing framework should you use? When should you run your test suite? There are so many things to learn and consider. At Checkly, we want to ease end-to-end monitoring so that you can focus on shipping excellent software instead of figuring out how you monitor and test it. But before getting into our latest feature addition, let me answer the above questions.
One of our goals here at Checkly is to make it easier for developers to ship excellent software. But let’s face it, getting features out is only a tiny fraction of the story. Fast-moving development teams also break things. And the more things you build, the more things can go wrong. And trust me, they will. This is where API and end-to-end monitoring helps. Define automated test suites that check all your properties constantly and guarantee that everything’s up and running. All the time.
We’re heavy end-to-end monitoring users here at Checkly and always experiment with how to architect our tests the best way. Over the past months, we’ve settled on a few workflows that make it much easier to spin up new tests, avoid code duplication, and make the entire test setup easier to manage. One of those strategies is to strictly separate concerns in our tests.
The monitoring and testing of public applications and APIs is challenging by itself. What should you test? How often should you run your tests? And who should be alerted? A scalable monitoring setup includes many hidden details, but technically it’s straightforward. Call public APIs and see if they do what they’re supposed to.
Today, I'm excited to share the release of a long-planned and requested feature - our new Check Overview Page. Until now, Checkly enabled you to troubleshoot single alerts, but a deep dive into the long-term performance trends was limited. That is not the case anymore. In the new Check Overview, we’re introducing the enhanced analytics in four distinct categories: The update is focused on two important outcomes.
We all know that pay is just as hard as it is important. Having a team distributed over 11+ countries makes pay even harder than in a traditional setup. I joined Checkly in mid-2021 with the promise of a fair and transparent culture in a remote tech startup and my goal was clear: make Checkly one of the best employers in our industry. A topic that I wanted to tackle early on was pay. How can we make pay less nebulous and more transparent, fair, and predictable?
One of Checkly's strengths is the capability to monitor key transactions on your site. It'd be missed opportunity if we didn't reuse it to monitor our own product! But for some important flows that comes with a couple of pitfalls. In this post, we'll take a closer look at how we monitor one of our top key flows: signup.
