From $17K to ~$1K: How We Optimized Azure Log Analytics Costs
Introduction Cloud costs do not always rise because of growth. Sometimes they rise because of configuration. That was exactly the case in our environment. We noticed that Log Analytics costs had climbed to roughly $17,000 per month . At first, nothing obvious stood out. There were no major application changes, no large-scale onboarding of new workloads, and no sudden increase in operational activity. But once we reviewed the ingestion data closely, the real issue became clear: a logging configuration was generating far more data than was actually needed. This post explains what we found, what we changed, and how the environment moved from a high-cost logging model to a much more efficient one while still keeping the right operational and security visibility. The Problem: High Log Analytics Ingestion The first step was to understand which tables were driving ingestion. Using the Usage table in Log Analytics, we reviewed billable ingestion over time and by data type. The results s...