Operations | Monitoring | ITSM | DevOps | Cloud

For many software engineers and developers, using standard libraries or built-in objects is just not enough. To save time and increase efficiency, most developers build on work done by others. Whatever the coding problem, there is likely another programmer who has already created a solution for it. There is usually no need to repeat the problem-solving process. This principle is known as Do not Repeat Yourself or DRY.

An on-call schedule tells you and everyone in the team who will be the first responder when an issue happens in production. The on-call team member is responsible for investigating the issue, either fixing the issue herself or adding other people who can help fix it. Having an on-call schedule is important for building reliable systems because making someone responsible for production issues makes sure that they're not ignored.

Adding alerts across your monitoring tools is taking a proactive approach to reliability. But if there are too many alerts, then it can become counterproductive because team members will start ignoring alerts or remove the alerting altogether. Which is why you need a systematic approach to adding alerts and dealing with them.

As a consumer, you know how you respond to slow sites. You hit the back button or close the browser. As a business owner, you’re well aware of this. You’re a consumer, too, after all. So, you know page load time and conversion rate are related. But how exactly? How does it affect the bottom line? In this article, we’ll analyze how page load time affects conversion rates and by how much.

DevOps has great potential; when it’s done right, it offers organizations improved collaboration, quick innovation, better quality, and shorter delivery cycles. But the reality is that some businesses don’t carry the DevOps process through to the data layer.

If you shudder thinking about compilation for different platforms, I know the feeling. One of the Java promises, the WORA (Write Once, Run Anywhere) principle, while revolutionizing platform independence, it stopped short of one more step – to be able to deploy anywhere. Personally, I think that WORADA sounds awesome, but I guess before Docker it didn’t occur to people that eliminating “works on my machine” is as simple as shipping your machine.

Catchpoint makes parenting a saner sport! OK, that’s not the usual use case. But much as I know it sounds crazy, I used Endpoint Monitoring to explain to my 11-year-old gamer that I’m totally innocent. The reason she is having gaming lag and lost connections is not because of her parents’ poor home Wi-Fi or her old PC – and she doesn’t just have to take my word for it. Here, let me explain.

Last year, businesses started focusing more on accelerating digital transformation initiatives to meet growing customer expectations and deliver consistent digital experiences from anywhere—no matter the product, service, or industry. PagerDuty partners with thousands of organizations to help reimagine digital operations and deliver real-time, digital experiences to their customers when it matters most.

Most of us who work in IT understand the concept of basic monitoring. It is not that it is an irrelevant concept, but rather, it is essential for any infrastructure, either manual, by reading logs and checking machines and services; semi-automated, using custom-made scripts or, the safest and most recommended, using a specific tool such as Pandora FMS to centralize your monitoring. But what is synthetic monitoring? We will see that throughout this article.

Recently, we added a new derived column function to Honeycomb, INGEST_TIMESTAMP(), which can help customers debug event latency and/or inaccurate timestamps. A meaningful minority of the events sent to Honeycomb are already old when they arrive, and a very special few claim to have been sent from the future. Has this happened to you? Let’s do an experiment.