Currently, customers use the Az Portal to navigate to the "Diagnostics Settings" and select the logs they would like to send to their Log Analytics workspace. These logs are directed to the "AzureDiagnostics" table in Log Analytics, which already includes the most used columns for Azure services. If a log includes a column that doesn't yet exist in the AzureDiagnostics table, that column is added the first time that data is collected. However, if the table already has 500 columns, any new columns are added to an “AdditionalFields” column, making it difficult for customers to search and analyze their logs. Due to the myriad Azure Resources that can send data to the AzureDiagnostics table, it is highly susceptible to blowing past the 500-column limit. Log Analytics as it currently exists can be challenging and costly for the customers, with a pricing structure of the default “analytics log” data plan.
Providing an option to enable "Resource Specific" in Log Analytics can enhance query performance and optimize costs. "Resource Specific" supports the “Basic Log” plan with a pricing structure lower than than "analytics log" plan in exchange for a shorter retention period of 8 days with search capabilities for debugging and troubleshooting.
Currently, customers use the Az Portal to navigate to the "Diagnostics Settings" and select the logs they would like to send to their Log Analytics workspace. These logs are directed to the "AzureDiagnostics" table in Log Analytics, which already includes the most used columns for Azure services. If a log includes a column that doesn't yet exist in the AzureDiagnostics table, that column is added the first time that data is collected. However, if the table already has 500 columns, any new columns are added to an “AdditionalFields” column, making it difficult for customers to search and analyze their logs. Due to the myriad Azure Resources that can send data to the AzureDiagnostics table, it is highly susceptible to blowing past the 500-column limit. Log Analytics as it currently exists can be challenging and costly for the customers, with a pricing structure of the default “analytics log” data plan. Providing an option to enable "Resource Specific" in Log Analytics can enhance query performance and optimize costs. "Resource Specific" supports the “Basic Log” plan with a pricing structure lower than than "analytics log" plan in exchange for a shorter retention period of 8 days with search capabilities for debugging and troubleshooting.