Your Log Analytics workspace ingests 80–120 GB/day. You must retain data for 120 days, ensure no logs are dropped even on peak days, and reduce cost variability. Which configurations should you apply?

Setting the workspace to a 100 GB/day commitment tier is correct because your daily ingestion averages 80-120 GB. A commitment tier offers a discounted price compared to Pay-As-You-Go and helps reduce cost variability by providing a predictable daily rate, even if you ingest slightly more or less on a given day. While 100 GB is slightly below your peak, it's the closest available tier that balances cost and capacity for your average use, and you will pay the Pay-As-You-Go rate for any data exceeding the commitment tier. Setting workspace (or table-level) retention to 120 days directly meets the requirement to retain data for that duration. Enabling a Daily Cap at 90 GB and choosing "Stop ingestion" would cause data loss on peak days (80-120 GB/day), violating the requirement to ensure no logs are dropped. Moving all tables to Basic Logs is incorrect because Basic Logs have limited query capabilities and a shorter retention period (8 days), which does not meet the 120-day retention requirement.