Operations | Monitoring | ITSM | DevOps | Cloud

Observability is a new term that’s slowly entered the mainstream over the last two years. Today it’s used in the context of monitoring, but it’s much more than that. And it also goes way beyond visibility. So, in this blog, we set out to explore observability vs visibility and find out, what’s the difference? In a recent podcast, our friends at Riverbed neatly explained that seeing and observing are two different things, and can be compared to hearing vs listening.

The CNCF Annual Survey 2021 is in and makes for some very encouraging reading for the future of Kubernetes and its place in the tech landscape. The 2021 survey was the biggest yet, with some 3,829 developers, engineers, architects, and C-level execs in the cloud native space taking part. Here are some of our key takeaways…

Site Reliability Engineering (SRE) practice was established by Google nearly 20 years ago, and was popularized with Google’s monumental SRE Book. Everyone’s been attempting to follow that iconic path ever since.

AWS currently offers over 200 services. Some of those make up the AWS Cost Management suite. This group comprises AWS Cost and Usage Report (CUR), AWS Budgets, AWS Cost Explorer, AWS Cost Categories, and AWS Cost Anomaly Detection. Budgets and Cost Explorer are an excellent pair of complementary tools in this group. They have similarities that cause users to wonder if they need both and, if so, why. Here is a brief overview of the differences between AWS Budgets and Cost Explorer.

Are you surprised? Are you under where are the first four tips? I start this series of blog posts on my blog, and you can see and read the previous Best practices, Tips, and Tricks here: And I will be sharing some of them here and others on my blog. So stay tuned for both blogs. Of course, the most recurring task is adding comments to our triggers and actions, but it is always good to know you to delete them. Some of you may be thinking that is a trivial task, simple like adding a comment.

Read a blow-by-blow analysis of two of the heavyweights in world of DevOps: when should you bet on Terraform, and what calls for Kubernetes?

To supervise the behavior of distributed applications and track the origin of service failures and downtime, developers often use traditional monitoring technologies and tools. However, this approach can fall short in its ability to measure the overall health of modern cloud-native architectures, which can span multiple hosting environments and encompass hundreds of microservices.