The widespread shift to remote working in response to the COVID-19 pandemic has been a disruptive change for countless businesses; some 13% of organisations say they have faced major disruption. But at Canonical, remote working has long been the status quo for many of our teams. In spite of the challenging circumstances in which we all find ourselves, Canonical has been able to continue to operate and support our customers despite their working practices undergoing significant changes.

In this article I’ll be sharing my own lessons learned with Dashbird in building reliable Well-Architected serverless applications and the highest impact areas to focus on no matter where you are in the Serverless journey.

Working with the right AWS provider can make or break a company, but many companies discover that after a few years, what was once a great fit just doesn’t work anymore. Over time, your needs change, and the provider you’ve been with for years might not be able to provide what you need. Alternatively, maybe your AWS provider simply isn’t living up to your expectations, or perhaps your company is looking to redesign their cloud infrastructure. When this happens, what are your options?

As we continue from our previous post on FinOps vs. DevOps let’s review the primary challenge facing all cloud consumers – identifying and managing current and potential cloud waste. In other words, understanding how efficient your cloud strategy and implementation actually is.. Controlling your cloud spend through a simple visualization is the first step to tackle the problem. Cloud Analyzer, a Spot by NetApp cost optimization tool, is a great starting point.

When looking at an EBS volume in CloudWisdom, you’ll notice that in addition to the metrics we collect from AWS, we also create a number of computed metrics, one of which is netuitive.aws.ebs.iopsutilization. Simply put, IOPS Utilization compares the current number of IOPS that the disk is performing against the total IOPS capacity, and expresses this as a percentage. Thus, if you are currently running 1050 IOPS against a volume whose capacity is 3000 IOPS, the IOPS Utilization would be 35%.

When organizations think about the relationship between Kubernetes and cloud costs, they often focus on Kubernetes’ auto-scaling capabilities and what this means for optimizing compute resources. Kubernetes does allow organizations to provision compute resources more thinly, because the platform allows them to scale up automatically if there’s a demand spike in the middle of the night.

One of the mistakes organizations make related to Kubernetes costs is addressing them primarily after-the-fact, once the application is running successfully. There are certainly changes that can be made to improve efficiency once the application is running, but cost-control measures are best considered at the beginning, not middle or end, of the application lifecycle.

Logic Apps are a gift to the integration of business scenarios as they are quite easy to understand and integrate with other systems but there are some challenges faced by the users in real-time.

Now that we have configured the monitoring for a couple of Service types, we should have some data flowing in. The only thing that’s left now is to display this data in dashboards, so it makes sense to us. In this blog let’s talk about displaying in data in SquaredUp. Since its coming from a Management Pack like any other data, it is actually pretty much the same as treating any other Management Pack in SCOM, with different classes.

In this article, we are going to look at two new visualizations from SquaredUp for Azure: Summary Grid and Summary Bar. Read on to learn how exactly they can help you easily summarize your Azure resources.