Operations | Monitoring | ITSM | DevOps | Cloud

Monitoring began by using software agents to capture data from infrastructure, operating systems, and applications. These agents would collect metrics and events from these systems to understand the health of the underlying system and the applications. This is what infrastructure monitoring is today.

At the end of October 2017, Microsoft announced the release of Azure Kubernetes Service (AKS), its hosted version of Kubernetes. If you’re new to AKS and curious about how to get a proof of concept (PoC) set up in your environment, read on. In this AKS tutorial, you’re going to learn, step-by-step, how to get an Azure Kubernetes cluster built with AKS.

In a previous blog post I discussed the complexity of securing Kubernetes environments, and some best practices. Unfortunately, even if we follow best practices in setting up and configuring our system, we can never eliminate all the vulnerabilities.

Today, I’m excited to announce the Open Observability Conference – a virtual event on May 27th at 11:00am EDT providing a platform for learning, sharing and discussion of open source observability technologies for DevOps teams around the globe. Register for the Open Observability Conference here.

Cloud-native is the new standard for modern applications. This usually means container-based applications, using the popular Docker and Kubernetes platforms, and increasingly also service mesh platforms such as Istio and Envoy. With that, container security in general—and Kubernetes security in particular—is at the forefront of engineers’ minds. Docker popularized containers based on the good-old but little-used LXC Linux containers.

Company security usually depends on your ability to come up with a diverse set of passwords and then manage them. Remembering all of them is considered a tad too difficult for most mere mortals, so a number of password storage apps have emerged. But they too have to be secured, and ultimately results in inefficient access and flawed security. Single-sign on (SSO) is still preferred, but to make it effective, companies like Okta have to secure integration across a number of apps.

Multiline logs provide valuable information for developers when troubleshooting issues with applications. An example of this is the stack trace. A stack trace is a sequence of method calls that an application was in the middle of when an exception was thrown. The stack trace includes the line in question that encountered the error, as well as the error itself.

At Logz.io, our team has the opportunity to partner with many cutting edge technology companies and products from different trades. Many have a crucial mission and help save lives worldwide. In the fight against the novel coronavirus, telehealth is one such sector. It compels us to do all we can to support these organizations by improving application accessibility and performance for users who need it. One of our customers epitomizes this—Tyto Care. Tyto Care is a healthcare pioneer.