In a relatively short amount of time, Kubernetes has evolved from an internal container orchestration tool at Google to the most important cloud-native technology across the world. Today’s enterprises are adopting Kubernetes to speed up the development process and build and deploy modern applications at scale, and they’re doing so at an incredible pace.

Growth for an enterprise is an exciting thing, but it often presents a unique challenge for IT professionals. There are common roadblocks that are encountered when trying to upscale an IT management environment. In this second blog of our Managing IT Infrastructure at Scale series, we discuss how to find the happy medium between monitoring software scalability and ease of use.

An application is not just a small part of any business. It would be wise enough to say that an application itself is a company’s business in today’s digital world. This is the reason why application performance monitoring problems are the biggest hurdle for IT Teams and the growth of any business. Customer expectations from the application’s performance are changing every day. Today, customers don’t have patience and want to use any application flawlessly.

Monitoring vs observability – is there even a difference and is your monitoring system observable? Observability has gained a lot of popularity in recent years. Modern DevOps paradigms encourage building robust applications by incorporating automation, Infrastructure as Code, and agile development. To assess the health and “robustness” of IT systems, engineering teams typically use logs, metrics, and traces, which are used by various developer tools to facilitate observability.

Incidents are inevitable, and the reality is some of them are inevitably going to repeat themselves. FireHydrant has always strived to make the entire incident response lifecycle smooth, but up until today, common incident types were slightly burdensome for our customers. We decided it was time to help people make it easy to declare incidents using easy-to-use templates, which we’re deeming Incident types.

Contact our Kubernetes team We’re now well into 2021, and as we plan ahead for our roadmap and activities around Kubernetes for the year, it helps to look back and reflect on everything that took place for Canonical in the K8s space within the year that passed. Kubernetes has always been a crucial part of Canonical’s vision and contribution to the IT world.

Implementing SRE is fundamentally about shifting culture, but it often means adding new tooling and processes to your team's workflows to support that cultural change. Teams add new steps and checks to incident response procedures. Incident responders write retrospectives and create new meetings to review them. Engineers consult new tools like monitoring dashboards and SLOs. In other words, SRE creates another layer of consideration in development and operations.

In this article we explore the basics of monitoring Amazon Web Services (AWS) by feeding metrics to Grafana through Hosted Graphite’s agent and also through Hosted Graphite’s AWS add-on. This will allow us to monitor metrics from applications and servers hosted in AWS with clarity and depth. This article assumes you have created a Hosted Graphite account.

Although it is no surprise that Gartner is forecasting that overall public cloud consumption will grow by 18%, hitting $304.9 billion in 2021, Gartner’s research also indicates that the vast majority of organizations overshoot their cloud infrastructure budgets due to a lack of cost optimization approaches.

Today’s announcement of Longhorn 1.1, a Cloud Native Computing Foundation (CNCF) Sandbox project, is exciting news for users of Rancher, SUSE’s Kubernetes management platform, and the Kubernetes community. Longhorn is an enterprise-grade, cloud native container storage solution that went GA in June 2020. Since then, adoption has increased by 235 percent.