Operations | Monitoring | ITSM | DevOps | Cloud

Modern applications generate a deluge of telemetry data—logs, metrics, and traces—that hold the key to understanding system performance and reliability. However, managing this data effectively is a growing challenge for DevOps teams. Raw telemetry can overwhelm teams with complexity and noise even when collected via robust standards like OpenTelemetry.

If you use Checkly, eventually you'll be looking at alerts about something failing, and wonder how to debug a failed check. For most of us, the first thing we want to see is the video of a failed check run. Sometimes, though, our check doesn’t capture video. This guide will cover three common reasons a video doesn’t show up on a check run. This advice is general for Playwright as well as those running Playwright tests on Checkly.

“When are we going to tell users about this?” By the time your incident response team, it’s already too late. During an outage, communicating about downtime with your user base has three main drawbacks: Instead, it’s better to create a status page that automatically shares the status of all your services in a format that users can easily understand. You’ll build trust with your users as you proactively share service status, lessening the perceived impact of incidents.

We just released a fresh new view of the sidebar in the Checkly app. This decision was made after some extensive user research—and this is the story of how we got to the final solution.

In today’s cloud-native world, third-party APIs are everywhere. Payments, notifications, search, AI, analytics as modern applications are built on a web of external services. But what happens when one of those APIs slows down, starts throwing errors, or gets rate-limited? Suddenly, your users are facing issues, and you’re stuck asking.

On the first of every month we generate an extensive PDF report for every site. This report contains a summary of all check results for the month and is a snapshot available to you and your team via email and the Oh Dear dashboard. We keep the report history so each month can be viewed in a browser or downloaded as a PDF. This report can also be emailed to any email address - not just team members - perfect for keeping your customers informed.

APIs are a big part of how modern applications or services work. They act as bridges, allowing systems to talk to each other and share data. Whether it's logging into an app or making an online payment, an application programming interface helps make that process smooth. But what happens when an API suddenly stops working? Even a short outage can cause a disruption. It can break features, delay operations, and impact users and businesses alike.

SQL is just for querying relational data, right? Well, not necessarily! With our SQL Analytics feature, you can run SQL queries over all types of data from all kinds of backend stores. This gives you incredible flexibility and power – you can even combine different types of entity (e.g. a pull request and a pipeline run) in a single query. Equally, I could have datasets with job tickets from Jira, ServiceNow and Zendesk and combine them in a single query.

There are few things that can derail developer productivity and undermine your pipeline like a flaky test. Testing is the backbone of a good development process, ensuring that your code is as accurate and usable as possible. When these tests point towards faulty development, the impacts can be significant. This information is predicated on an assumption, however – the assumption that what the test says is accurate.