Azure Monitor Log Alert V2

Log Alerts have been available in Log Analytics for quite some time. Initially they were available via legacy Log Alert API that was specific for Log Analytics. In order to make Log Alert more native to Azure a new Log Alert API was available. With a few minor features like (custom webhook payload) that API was direct translate from the legacy one offering the same features. Now Azure Monitor team is introducing a new Log Alert that is named Log Alert V2. That new alert is using the same API but with new version. So if you use the API version 2018-04-16 to create Log Alert you are creating v1 and if you use version 2021-08-01 you are creating v2. Log Alert v2 will be generally available probably very soon as I have received e-mail notification containing the following information:

  • any API version like 2021-02-01-preview will be deprecated and replaced by version 2021-08-01
  • billing for Log Alert v2 will start from 30th of November.

This for me signals that before 30th of November or several weeks after the service will be generally available. I am not aware of specific information just the official e-mail notification leads me to these conclusions. The Log Alert v2 has been in preview for a couple of months which I have been testing and providing feedback.

Continue reading “Azure Monitor Log Alert V2”

Find The Resources Which Use Particular User Assigned Managed Identity

I have been busy lately (answering on Q&A, Bicep testing, working, etc.) which prevented me from writing new blog posts but I hope to do more blogging again. This blog post will be a quick tip.

If you have wondered in which resources a particular user assigned managed identity was used you can see that information quickly by using Azure Resource Graph. The query is very simple:

Continue reading “Find The Resources Which Use Particular User Assigned Managed Identity”

Finding Columns that are used by more than one service in AzureDiganostics table

AzureDiagnstics table is used by many Azure Services when you send diagnostic logs thus the 500 column limit that Microsoft is trying to fix for that table. When you hit that limit there is currently the described workaround but let’s say you have used one service that was sending logs and you no longer use that service. The logs associated with that service are yet to purged but you also want to clean up any custom columns that the service was using. That way you can free some slots for new custom columns for new services that will send logs to AzureDiagnostics table. Of course you can delete the custom column from Log Analytics blade but you do not want to delete a custom column that is also used by another service. This will be a short blog post that I will show you how to find if custom column is used by more than one service by using Kusto query language.

Continue reading “Finding Columns that are used by more than one service in AzureDiganostics table”

Storage Spaces Direct (S2D) Management Solution for OMS V2

As you may have heard Log Analytics has a new query language. When you upgrade solutions are automatically converted to this new query language but I wanted to provide better experience so I’ve updated the Storage Spaces Direct (S2D) solution. Continue reading “Storage Spaces Direct (S2D) Management Solution for OMS V2”