Alerts are important part of our monitoring and probably the most important one. Getting data and visualizing it is the foundation for alerts but in order to move to actual monitoring you need alerts. I can tell you nobody sits all day in front of dashboard and looks at visualized data. Alerts are also our knowledge of our applications and infrastructure gathered to help us when things are not going as planned. I wanted to write this blog post series for quite some time and I think this is the right time to do it. The reason for that is Classic Azure alerts are being deprecated and the vision of unified alerting capabilities is coming together and becoming more powerful… sort of. I will comment on parts that I think could and should be improved and hopefully they will be. I also expect some new features around Ignite as usually that is when Microsoft reveals some new stuff. They actually do it all the time it just the end development of some features matches Ignite conference time frame.
Lately I have seen some questions and discussions that I have also been involved around which management services/tools should be used when you are doing multi-cloud. Before diving into that area let’s first dive into the multi-cloud thingy. RightScale has report for year 2019 called STATE OF THE CLOUDREPORT that give us what is the current state of companies in that area. If we look at the report we will see that multi-cloud strategy is rising but if we look in the details the strategy of having multiple public or private clouds is actually starting to decline, slightly but still decline. I think that decline will continue over the next years. For me it makes sense if you have the bigger part of your cloud workloads in a single public cloud and may be some small part into another public cloud. My opinion is that it is better to put your bets into a single public cloud. I do not think there are much of benefits if you do multi-public cloud strategy. As for putting workloads on-premises the hybrid cloud strategy I think will be still valid at least for the next 10 years. With that said never the less there are still companies that have multi-cloud strategy with multiple public clouds. And this brings us back to our topic. You have probably heard similar questions like:
Lately you haven’t seen new blog posts by me due to diverting my community time and efforts towards Inside Azure Management book. As now I have finished most of my work on the book I can focus again on blogging.
I very often work closely with the ARM team by giving them feedback and features like Azure Resource Manager template language additions are appearing because of that feedback and I am sure the feedback by many other MVPs, partners and customers. Because of that I never settle for workarounds where you can do something natively within ARM template. I have previously blogged about an issue with deploying Azure Policy definitions via ARM template:
For the last a couple of years many Azure services has started to produce diagnostic logs and metrics. These two allows you to monitor and troubleshoot the Azure Services. Unfortunately still there are some services that are missing those. To pull diagnostic logs and metrics Azure Monitor has capability called Diagnostic settings which allows you to place them on Azure Storage, Event Hub or Log Analytics. Microsoft has done a good job to document many of diagnostic logs available but still I find some services that haven’t be documented. Luckily there is a way to find what diagnostic logs are available for a service (resource) and this blog post will focus on that.