Question 1

How much does cloud monitoring cost?

Accepted Answer

Cloud monitoring ranges from $0 (open-source self-hosted, free vendor tiers) to $200,000+ per month for enterprise deployments. The median mid-market team running 100 hosts with full observability spends $3,000 to $15,000 per month. Costs are driven primarily by host count, log volume, custom metric cardinality, and APM coverage. Verify current pricing on each vendor's pricing page before purchasing.

Question 2

What is the cheapest cloud monitoring tool?

Accepted Answer

Self-hosted Prometheus and Grafana is the cheapest in pure license terms (free), but requires platform engineering capacity. Among managed services, Grafana Cloud has the most generous free tier and lowest paid-tier pricing. New Relic's 100 GB free data ingest is the next most generous. Datadog and Dynatrace are positioned at the higher end of the market.

Question 3

What percentage of cloud spend goes to monitoring?

Accepted Answer

Industry research from independent and vendor sources puts the median at 7 to 8 percent of cloud infrastructure budget. Below 3 percent typically signals under-monitoring. Above 15 percent signals overspend and is a common trigger for cost-reduction projects. Microservices and Kubernetes-heavy stacks land at the higher end of the range.

Question 4

Why is my Datadog bill so high?

Accepted Answer

Bill spikes usually trace to one of: custom metrics generated from high-cardinality labels (Kubernetes pod, container, namespace), log indexing charges on top of ingest charges, APM span indexing above the included 1M per host, retention upgrades beyond the 15-day default, or container counting that bills each pod as a fractional host. See vendor pricing pages and our hidden costs page for the underlying mechanics.

Question 5

How can I reduce monitoring costs?

Accepted Answer

The highest-impact strategies in order: filter and sample logs at the source (saves 30 to 50 percent), control custom metric cardinality (saves 20 to 40 percent), sample APM traces at 5 to 10 percent (saves 15 to 30 percent), right-size retention to actual query patterns (saves 10 to 20 percent), and consolidate or migrate to open source where the team has capacity (saves 40 to 90 percent).