Every day, organizations face external threats as a consequence of exposing their services over the internet. An estimated 2,200+ attacks occur in a 24-hour period—or one attack every 39 seconds. Add the fact that an average data breach (one of many potential consequences of poor security) costs companies $4.45 million, and the need for strong security is impossible to ignore. Web application and API security is key to protecting your infrastructure, data, and users.

This is the last part of our 12-day Advent of Monitoring series. In this series, Checkly's engineers will share practical monitoring tips from their own experience. At Checkly, the commitment to reliability is not just a tagline; it's embedded in our DNA. As software engineers, we understand the critical importance of dogfooding—using our own product to ensure its robustness and effectiveness. This approach holds immense value, especially since Checkly is designed for observability.

The two key pillars of building reliable applications are: testing and monitoring. With testing, you can verify that each pull request works before it’s merged and deployed to production. Just testing isn’t enough, though. You also need to make sure that the application continues to work on production. Database rollovers, third-party outages, and unexpected spikes in traffic can all cause issues that need to be detected.

Cribl Stream is awesome at routing your server logs and making your job easier, but could it help you outside of work and potentially make your personal life easier? The short answer is: Yes. I’ve personally used Stream to build a notification system to inform me when certain products go on sale or when fully booked appointments become available. In this blog, I’m going to take this a step further and show you how to.

Cloud-based database providers often provide great observability out of the box. But, what if you’re developing a tricky feature locally and need more details about what your local Clickhouse is doing? There are many options, but if you’re a numbers and graphs person like me, you’ll want to be able to view the inner workings of Clickhouse in something like Grafana.

This is the ninth part of our 12-day Advent of Monitoring series. In this series, Checkly's engineers will share practical monitoring tips from their own experience. As a Checkly user, you’ve always had access to our two core check types: API and browser checks. API Checks are much cheaper, and therefore only run a curl-like request against the endpoint of your choice.

If you have large(r) customers, there is a point where they ask you for service-level agreements, or short SLAs. These are customer contracts defining different aspects of your service and what you guarantee for them. One common agreement is around availability, or, colloquially speaking, uptime. Your contract might state, and I am not a lawyer, that you guarantee that your service (or core parts of it) is available 99.99% of the time of a given period, mostly per month, quarter, or year.

Table of contents This is the seventh part of our 12-day Advent of Monitoring series. In this series, Checkly's engineers will share practical monitoring tips from their own experience. At Checkly, we manage various scheduled jobs, some of which play a crucial role in our application's functionality, and others exist to support different teams within Checkly.