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.
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”