Keeping Log Analytics Costs at Bay: Budgets, Alerts and a Kill Switch You Actually Test

Short summary

Log Analytics costs spike unexpectedly when diagnostic settings, connectors, and verbose logging compound across sources. This article walks through three-layer cost control: prevention (data filtering and retention tuning), detection (staged budget alerts), and circuit-breaking (automated ingestion caps via Logic App). Implementation uses Cost Management budgets with thresholds at 50%/75%/100%, with safety checks to prevent accidental re-triggering.

• •Log Analytics costs spike from compound diagnostic settings, connectors, and verbose logging
• •Three-layer control: prevention (data filtering), detection (staged alerts), circuit-breaking (automated caps)
• •Implement with Cost Management budgets at 50%/75%/100% thresholds; only the 100% threshold triggers Logic App automation

Generated with AI, which can make mistakes.