Operations | Monitoring | ITSM | DevOps | Cloud

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.

AWS Lambda can be an easy-to-implement solution for those looking for serverless application deployments and operations. However, how can you be sure that you are getting the most for your money when it comes to utilizing this service? This guide will explain some of the tools and resources at your disposal — whether you’re utilizing the AWS console, trying to optimize your code and design, or a combination of the two.