Operations | Monitoring | ITSM | DevOps | Cloud

Checkly

How to add Type Checking and Linting to your Playwright Project

If you bet on end-to-end testing or even synthetic monitoring, there’s a high chance that you use Microsoft's Playwright. And if you have Playwright in your toolchain, you probably adopted TypeScript, too. It's an easy choice because of its rock-solid auto-completion and type safety. With this setup, you can enjoy the beautiful DX (developer experience) and safely refactor your ever-growing code base without worrying about runtime exceptions because of TypeScript's type checking, right? Wrong!

Checkly Kick-Start: Writing your first site monitor

Join Nočnica Mellifera for the Checkly Kick-start. You'll learn: How to get started and write your first page monitors — Anyone can monitor their site with Checkly, and you'll get a demonstration on getting started. Best Practices for monitoring — From monitoring as code workflows to alert configurations based on your SLA, learn how experienced professionals use synthetic monitoring. Advanced skills for automation — Ever wanted to check your site by comparing screenshots? Or create checks that simulate network slowdown? Learn how to simulate complex scenarios with Checkly and Playwright.

Observability as Code Explained: Benefits & How to Get Started

Traditional monitoring has become insufficient for managing complex systems. Modern infrastructures consist of numerous interconnected services, and simply monitoring individual metrics and logs fails to provide a comprehensive view. This is where observability becomes crucial.

An in-depth guide to monitoring Next.js apps with OpenTelemetry

This guide goes into the fundamentals, practical applications and tips & tricks of using OpenTelemetry (OTel) to monitor your Next.js application. OpenTelemetry is gaining (a lot) of momentum outside of its historical niche of distributed, micro services based application stacks. But, as it turns out you can just as well use it for more traditional, three tiered, web applications and it comes with a host of benefits.

Why "page.goto()" is slowing down your tests

In this video, we dive into Playwright's "page.goto()" and understand why it could be slowing down your end-to-end tests. We start with an example script and then walk you through the Playwright UI mode to understand how resource loading can delay the "page.goto()" call. We also look into the different "waitUntil" configurations and check how they affect the speed of your tests. Enjoy, and drop any questions or comments below!

Why "page.goto()" is slowing down your Playwright tests

When you invest time and effort into creating a well-running end-to-end test suite or adopt Playwright synthetic monitoring with Checkly, you should focus on two things. Your tests must be stable because few things are worse than an unreliable test suite. But also, your tests must be fast because no one wants to wait hours to receive the green light when you're on the edge of your seat to deploy this critical production hotfix.

Playwright at Scale

When adopting Playwright, it can be tough to know if you're following the right design principles for a process that will work at scale. For those Cypress users, check out Cypress at Scale. Join Jonathan and Filip as we explore how mature organizations and effective teams adopt Playwright. We'll cover what we've seen in the wild and key considerations. — Fundamentals & principles: You'll understand what Playwright is and its design principles.

Monitoring as Code and Checkly Listed in the Gartner Hype Cycle for the Second Consecutive Year

I'm excited to share that Gartner has included Monitoring as Code (MaC) as an emerging practice to their Hype Cycles for SREs again, the second year in a row. Since we founded Checkly, our vision has been that monitoring should sit in your repository, be codified, and scale with your software development. There is no alternative to MaC as it allows your engineering team(s) to work together, create and maintain checks, and ultimately own their monitoring.

How to Monitor JavaScript Log Messages and Exceptions with Playwright

Monitoring JavaScript log messages is how you know, at a basic level, what the browser’s JavaScript engine is doing in detail. Playwright provides an efficient way to listen for console logs and uncaught exceptions in your pages. This capability is invaluable for developers and testers aiming to catch and resolve issues early in the development cycle. This article will guide you through the process of setting up Playwright to monitor JavaScript logs and exceptions, enhancing your testing strategy.