AZ-305 · Question #325
Hotspot Question You have an Azure subscription that contains the resources shown in the following table: Log files from App1 are registered to App1Logs. An average of 120 GB of log data is ingested…
To minimize Log Analytics costs while ensuring all logs are ingested and minimizing alert impact, you should modify the App1Logs workspace by configuring a Basic or Auxiliary log tier (or enabling a data collection rule with transformation) to filter out non-error logs before…
Question
Exhibits
Explanation
To minimize Log Analytics costs while ensuring all logs are ingested and minimizing alert impact, you should modify the App1Logs workspace by configuring a Basic or Auxiliary log tier (or enabling a data collection rule with transformation) to filter out non-error logs before ingestion, or implement a table-level data retention and tier strategy. The correct approach is typically to modify the Data Collection Rule (DCR) associated with App1 to add a KQL transformation that filters or reduces the volume of ingested data, sending only relevant log data to the analytics tier while keeping error detection intact. This reduces billable ingestion volume (saving cost on 120GB/day) without dropping error-level logs that trigger the Azure Monitor alert.
Topics
Community Discussion
No community discussion yet for this question.

