Azure with Danidu

Recently I got to chance to work with Azure Bicep. I previously had experience with ARM templates. My first impression to Bicep was "WOW", It seems pretty cool and I started enjoying scripting with Bicep, but there were some moments when I felt some bad feelings. All in all it's pretty awesome :) So Started writing this blog to show how to best use Bicep templates. I have a similar vlog series also. My aim in this blog series is to build a full working environment with Bicep having all the bits and pieces tied together and later on maybe we can tidy up a few things. Following is the environment I want to build when using bicep we can create modules and main files. what happens is we can call modules in main files or within separate module files. Similar to OOP :) quoting MS Documentation about Modules "Bicep enables you to break down a complex solution into modules. A Bicep module is just a Bicep file that is deployed from another Bicep file. You can encapsulate comp...

Howdy Folks It's time to discuss Azure Monitor costs, As you all know Microsoft merge most of their logging service solutions under the Azure Monitor umbrella. And most of the services share a common log collection location for this service which is the Log Analytics workspace. The following diagram explains the services under each category. Next what we need to understand is how we get charged for Log analytics workspaces. So that we can work on reducing the costs. As per the Microsoft documentation, we are getting charged based on Data Retention Data Ingestion let's do a quick calculation and see how this going to affect our bill. Let's take an example scenario, let's assume we have a few Azure workloads that generate 2GB data every day and we are ingesting that to log analytics to retain for 90 days As per the above example, we can clearly see our charges will increase with data ingestion capacity but not much with data retention. How to Find the Utilization? Now th...