SaaS Evaluated Find a tool

Log management cost worksheet

Compare how Datadog and Grafana Cloud charge for ingesting, indexing and keeping the same log stream.

One log stream, kept for a month

This example uses 500 GB and 50 million events per month. The team needs 30 days of searchable logs. All figures are illustrative US dollars per month before tax, based on public rates checked November 19, 2026.

TreatmentDatadog, annual rateDatadog, monthly rateGrafana Cloud Pro estimate
Keep everything$175.00$200.00$224.00
Send everything, keep 20% searchable$75.00$80.00$64.00
Keep 20% by filtering before sending$35.00$40.00$44.00

All rows model 30-day searchable retention. In the two filtered rows, assume the kept records represent 20% of bytes and 20% of events, or 100 GB and 10 million events. Real pipelines can drop many short messages without removing the same fraction of bytes.

Datadog adds $0.10 per ingested GB to the applicable 30-day indexing rate of $2.50 per million events on annual commitments or $3.00 on monthly commitments. At its $3.75 on-demand rate, indexing all 50 million plus ingestion would cost $237.50 in this example.

Where Datadog and Grafana Cloud start charging

Put the same filtering rule in two places and compare the resulting usage lines before relying on the estimate.

MeterKeep everythingDrop after receivingDrop before sending
Datadog ingestion500 GB500 GB100 GB
Datadog indexing50M events10M events10M events
Grafana processing500 GB500 GB100 GB
Grafana writing500 GB100 GB100 GB

Grafana Cloud Pro is modeled with its $19 platform fee, $0.05 per processed GB and $0.40 per written GB after the 50 GB write allowance. For 500 GB sent and 100 GB written, the arithmetic is $19 + $25 + $20.

The scenarios assume no volume discounts, archives, rehydration, extended retention, excess queries or other observability products. Grafana's rates can vary with usage, so use the billing dashboard during the trial.

One quiet day and one incident window

Capture one weekday and one high-volume incident window in a staging environment. Use the same service allowlist and operational queries on both platforms.

Trial stepRecordPass condition
Measure at the collectorUncompressed GB and event counts by service and environmentThe pre-filter counters reproduce the volume sent.
Apply a selective filterKeep incident errors and traces needed for investigation. Record excluded event and byte counts.The team can still retrieve the failure signatures it uses during incident response.
Reconcile usageCompare received, processed, written and indexed volumes with the vendor usage report.The billable meters explain the sample bill. Separate query, archive and retention charges.
Repeat the incident queryRun the same search using the intended retention and filter configuration.The required incident window and evidence are readable under the modeled tier.

Sources