Operations | Monitoring | ITSM | DevOps | Cloud

Frontend technologies typically talk to several services in your backend, and those services talk to other services. At the root of every issue is a single event that causes a domino effect. A domino effect that impacts every operation from the first experience on the frontend to the backend API call. Sentry can show you how these exceptions and latency issues impact every one of your services. For example, take the ever common and seemingly simple to resolve 500 - Internal Server Error.

One of the most critical aspects of monitoring your digital assets is getting a timely alert when something goes wrong. Even when you finish building a monitoring stack and expose metrics on a beautifully designed dashboard if you cannot notice abnormal behaviors and fail to take pre-emptive or follow-up actions swiftly, this means your monitoring system does not serve the purpose.

Uptime monitoring. You keep hearing us talking about it and you know why it’s important, hey, you might even have a StatusCake account. But do you know what to do if you do experience website downtime? Let’s do a little quiz. Your website has suffered two hours of downtime. Do you: If you answered a, you might be a lost cause (I’m only joking, you should just definitely read to the end of this post), and if you answered d, crack out the sales bell and start dinging!

A couple of weeks ago, we had a great time hosting the workshop you can see below with Vlad Mihalcea. It was loads of fun and I hope to do this again soon! In this workshop we focused on Spring Boot performance but most importantly on Hibernate performance, which is a common issue in production environments. It’s especially hard to track since issues related to data are often hard to perceive when debugging locally.