Operations | Monitoring | ITSM | DevOps | Cloud

On December 7, 2021, Amazon’s cloud services recently suffered a major outage that not only affected Amazon services, but also many third-party services we use day-to-day, including Netflix, Disney+, Amazon Alexa, Amazon deliveries and Amazon Ring. Causes for the outage, which began at 7:30 am PST and lasted nearly seven hours, were detailed in a Root Cause Analysis report published by AWS that shed light on factors that may have contributed to the extended length of the disruption.

Source: APM in the new normal, survey by eG Innovations and DevOps Institute Cloud adoption is increasing at a rapid pace. The eG Innovations & DevOps Institute APM survey indicates that 88% of organizations are using at least one form of cloud technology. Organizations move to the cloud for agility – they can deploy and have applications running in the cloud in minutes. Cloud computing also offers options for high availability, automated backups, and such.

Self service analytics are becoming increasingly popular and essential in this data-driven world. For many businesses, there is a growing need for their internal departments to access their data and business intelligence and harness its power themselves. Traditionally, business intelligence processes are the purview of IT teams and data specialists.

As of yesterday, the team behind Go has released a new version 1.18 with some significant changes to the language. Those of you who want to start using these new features are in luck: you can do it right away on Upsun. If you’re already using Go on Upsun, you can upgrade by changing the number in the type key of your app configuration. In your.platform.app.yaml file: If you’re not yet using Go for your project, now’s a great time to give Go a try.

In this blog post, I follow on from my previous blog on AWS CloudWatch Part 1 of 2 to explore how you can go beyond basic agentless CloudWatch monitoring by deploying the CloudWatch agent and some of the key information and planning you need to do this. I’ll also cover how eG Enterprise offers out-of-the-box functionality to avoid complex JSON scripting or tooling to implement monitoring.

We are going to deploy a Go application directly from your repo to AWS with Cloud 66. Any application using any language on any framework can be deployed with Cloud 66 as long as it has a Dockerfile. Note: Rails applications are exceptions as we deploy them natively. If your application does not have a Dockerfile, we will suggest one for you based on your code. However, we would recommend reviewing what we have suggested and making sure the Dockerfile meets your requirements.

This blog post discusses some of the best practices for balancing the costs of cloud traffic monitoring while maintaining a reasonable level of visibility. Progress Flowmon 12 has introduced the processing of native flow logs from Google Cloud and Microsoft Azure, plus it has enhanced support for Amazon Web Services (AWS) flow logs.

The global footprint of Microsoft Azure is made up of physical infrastructure of over 200 data centres and connective network components, arranged into regions, and linked by a large interconnected network. Each of the Azure data centres provides high availability, low latency, scalable cloud services close to users to improve reliability and speed. In this blog, we look at the Azure Regions, and explain the benefits of using a direct connection to access Azure infrastructure.

Business leaders and team members face countless decisions every day, some of which are certain to have an impact on the future of a company. Perhaps the most impactful to a SaaS company’s bottom line are financial decisions related to the cloud. Engineers and team leads need to know which cloud architecture choices are worthwhile and which should be scrapped in favor of a more cost effective model.