The time has come to publish the Inside Azure Management v4 book. This is the only free book that focuses on Azure Management. If you want you can also support us with purchase from Amazon. Links for both the free and purchasable version you will find below. It is needless to say that the authors of this book Pete Zerger, Tao Yang and Kevin Greene and me have put a lot of effort. Additionally also Ryan Irujo, Alexandre Verkinderen and Bert Wolters have put also a lot of effort in authoring of certain chapters. I would like to thank to all authors for the great work. Comparing v3 to v4 release we have tried to make the existing content better with providing even more examples. Overall we have followed the same guidance as before: trying to give you less content that is already available and focus on tips, tricks, scenarios and examples. Any feedback you can send it to us via e-mail: insidemscloud (at) outlook.com. I hope that you will enjoy our work and you will find it useful.
With the recent capability of setting retention period for Log Analytics data per table a lot of new possibilities of managing and retaining your data pop-up. A common scenario is that you may have a lot of performance data which may be logged every minute or even every 10 seconds. You need that data in such short intervals in your Log Analytics workspace only for the past month or so but you do not need such granularity for older data. At the same time it is good to have some summarization (aggregation) of that data for longer period due to compliance, analysis, etc but there is a cost associated when you retain a lot of data for longer period. By using serverless and the new per table retention capability now you can achieve this and save cost. In this blog I will show you how you can achieve this with simple example.
We continue our journey in Azure Monitor Alerts. This time we will cover alert type that is not part of Azure Monitor specifically but my opinion is that every Azure alert should integrate somehow with Azure Monitor so we have one consistent alert experience. The alert type that we will cover today somehow achieve this. This alert type is cost management alert or budget alert.
While discussing Azure/OMS topics in the community I often see incorrect usage of OMS (Operations Management Suite). That is understandable of course as Microsoft hasn’t done good job at clearing out all the terms but I still think we should be using the correct term when posting questions or discussing OMS in forums and other sites. This can help us communicate better between each other and especially in forums could result to answering question faster. As we the move from OMS Portal to Azure Portal it was about time to write this blog post which I’ve intended to do for quite some time but always delayed due to different circumstances.