Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes is today the most well-known container scheduler used by thousands of companies. Being able to quickly and automatically scale your application is something standard nowadays. However, knowing how to do it well is another topic. In this article, we'll cover how pod autoscaling works, how it can be used, when it's exciting and not, and finally, we'll cover it with a Qovery usage we have internally.

Whether you are a site reliability engineer, DevOps engineer, or application developer, you need visibility into the health and performance of every service you run or support. But in complex, dynamic environments, it can be difficult to ensure that all services are accounted for.

Today’s customers see availability as a given. What do they really want? Bigger, better technology with new features and faster platforms. But, according to our recently released Moogsoft State of Availability Report, teams burn their time, money and energy on incident management. In fact, engineers overwhelmingly report that incident management takes up most of their time.

Conventional wisdom states that SaaS engineers don’t care about costs. They care about building an optimal product, regardless of the dollar signs associated with it. As a result, the finance team feels they must corral the engineers’ efforts and constrain them to work within an agreed budget. In fact, the FinOps Foundation’s annual survey consistently ranks “getting engineers to take action on cost optimization” as the number one challenge experienced by FinOps specialists.

For infrastructure administrators tasked with ensuring the reliable operation of their applications, the thought of a lurking cyberattack can be one to lose sleep over. An attack on your system and the services you provide could render your applications unresponsive, resulting in a security breach, or loss of data.