Operations | Monitoring | ITSM | DevOps | Cloud

With the rapid adoption of cloud, distributed systems and microservices are standard, resulting in increasingly complex environments. Once straightforward troubleshooting workflows have become chaotic, frustrating, and time-consuming. When something breaks, multiple teams are called to the table to prove they’re “not it”; each with their singular view of the problem.

As an AWS user, you know how important it is that your organization understands what you’re spending and why. AWS is a tremendously powerful resource, and when you have complete visibility into the cost efficiency of your AWS environment, you can use it to remove many of the scaling obstacles that companies faced in the past.

Synthetic monitoring in Cloud Monitoring tests the availability, consistency, and performance of a web application from a real user’s perspective.

As a developer, when I first stepped into the wonderful world Kubernetes, I was amazed at the endless configuration possibilities it offered for containerized apps. It felt like I was handed the most multifaceted tool for all my deployment needs.

In the last decade-plus, the cloud has undergone a torrid evolution. Born in 2006, the cloud didn’t face the same speed limits on evolution that we mortals do. Within years, the cloud had gone from competitive edge to competitive necessity; within a decade, specialized services like Kubernetes, Snowflake, and Datadog had emerged to help us use it more, more flexibly, and with a more data-driven strategy. As the cloud evolved at an exponential rate, so did the costs associated with using it.

Today, I’ll be covering troubleshooting Azure Virtual Desktop (AVD) issues. I’ll cover the common causes of problems beyond logon and how you can monitor and troubleshoot to identify the root-causes of issues and how to resolve them resolve them. For information on troubleshooting logon problems and slow logons, please see my previous article: Troubleshoot Slow Azure Virtual Desktop (AVD) Logons.