June and July are traditionally slow months. The sun is out, and there’s too much work reflecting off all our monitors for any of us to get much work done. For us, it’s doubly slow as we’re putting all of our efforts towards a big launch later this year. Still, some great stuff came out.
In this post we are going to demonstrate how to deploy a Kubernetes autoscaler using a third party metrics provider. You will learn how to expose any custom metric directly through the Kubernetes API implementing an extension service.
Debugging. It’s one of the most time-consuming ways of finding a bug. As a senior .NET developer, I can tell you that it’s best to avoid the necessity for debugging altogether by writing clean code that’s covered by automated tests. If you’re a senior developer yourself, you probably already know this. And if you’re a junior developer, now you know it too! However, the world isn’t binary.
We’ve changed Transaction steps and Multi-step API Monitoring steps to Transaction credits and Multi-step API Monitoring credits. In short: Steps are used to group your actions in your monitor definitions, and credits are used to buy Transaction or Multi-Step API monitors. Let’s explain that in more detail.
In the world of Software Engineering, observability seems to be the talk of the town. We discuss it at conferences, read about it in blogs or articles, and see it promised to us by vendor after vendor. But what is observability? What issues have recently evolved to make it such an integral concept? What strategies are engineers employing to ensure observability? And most importantly of all, why are engineers looking to achieve it?
If you’re not familiar with APIs, let’s run through a quick primer. API stands for application programming interface and refers to a set of tools and protocols that makes it possible to easily and efficiently access a software or hardware system from the outside.
Tools like Rollbar have changed the way development teams are recording and managing their exceptions. What used to be a very personal developer-by-developer activity can now be a team-wide tool for greater transparency, and increased application quality. But many still treat exception monitoring as a developer activity, and they are not leveraging its benefits across all environments, from development to stage and integration, to systems testing and production.
