Free tool

How many custom metrics does one metric create?

Enter a metric and its tags with the number of distinct values each, or paste a sample of series. See the custom metric count on Datadog or CloudWatch, what it costs a month, which tag drives it, and what dropping or bucketing that tag saves.

  • List prices come from the vendor's own pricing page, with the date we checked them. You can enter your contract price.
  • Every result shows its formula and inputs, so you can check the math.
  • Everything is calculated in your browser. Nothing you enter or paste is sent anywhere.

Loading prices…

The metric

Vendor

Tags and their distinct values

Datadog counts the host tag too. Mark a tag "nested" if every value of it belongs to one value of another tag (like state under city): it adds no new combinations.

Or paste a sample of series

One series per line: name{tag:value,tag2:value}, Prometheus name{label="value"} 12, or a DogStatsD line name:1|c|#tag:value. From a /metrics page, the Metrics Summary or your logs. It is read in this tab only.

    Price

    Prefilled with the list price. Enter your contract price if it differs.

    The allotment is pooled across the account.

    At the source, the tag is never sent. With Metrics without Limits, it is still ingested (and billed for ingestion) but not indexed.
    They use up the allotment or the cheaper tiers first. Leave 0 if you don't know.

    How to check your own account

    Find the series-heavy metrics

    In Cost Explorer, filter Service to CloudWatch and group by Usage type. Look at MetricMonitorUsage, GMD-Metrics and Requests; each carries a region prefix. A jump that lines up with a deploy or a scaling change means new series or new hosts.

    In Datadog, open the custom metrics usage page and list the top metrics by series count. In Prometheus, find the series-heavy metrics with:

    topk(10, count by (__name__)({__name__=~".+"}))

    For each top metric, look for tags that change per request, user, pod or container, such as user_id, request_id, pod_name or a container ID. Check your APM agent config too: HTTP paths with IDs in them and query parameters are common culprits.

    What can go wrong: dropping a tag that a dashboard or monitor filters on breaks it without an error. Search your dashboards, monitors and recording rules for the tag first. Then remove it at the source, drop it in the pipeline (Prometheus metric_relabel_configs or an OpenTelemetry Collector processor), or in Datadog index only the tags you query with Metrics without Limits.

    From Gotcha 9 of our free guide, 12 cloud bill gotchas, and how to get the money back.

    Privacy

    Your numbers stay on this page

    • The estimator runs in your browser. The page loads its own price list from this site and sends nothing you type or paste.
    • Its Content-Security-Policy only allows connections back to this site, and it loads no third-party scripts, fonts or trackers.
    • A shared link keeps your inputs after the #. Browsers never send that part of a link to a server.
    • The only request with something you typed is the optional email signup. It sends your email address and the tool's name, nothing else.

    Want us to look at the real thing?

    Book a free 30-minute consult: we'll look at your bill with you, no obligation and no sales pitch. Or check your own cloud bill first with our free Cloud Bill Gotchas Checker.

    Book a free 30-minute consult