If a metric is not submitted from one of the 400+ Datadog integrations it’s considered a custom metric(1). Custom metrics help you track your application KPIs: number of visitors, average customer basket size, request latency, or performance distribution for a custom algorithm.
A custom metric is identified by a unique combination of a metric’s name and tag values (including the host tag). In general, any metric you send using DogStatsD or through a custom Agent Check is a custom metric.
Note: Users with the Datadog Admin roles can see the monthly average number of custom metrics per hour and the top 500 custom metrics for their account in the usage details page. Learn more about how custom metrics are counted.
A Datadog custom metric has the properties below. Refer to the Metrics Introduction documentation to learn how to graph metrics within Datadog.
|The name of your metric.|
|The value of your metric.|
|The timestamp associated with the metric value. Note: Metric timestamps cannot be more than ten minutes in the future or more than one hour in the past.|
|The set of tags associated with your metric.|
|The type of your metric. See the metric type documentation.|
|If the |
The following custom metric naming convention must be followed:
Note: Metric names are case sensitive in Datadog.
There are multiple ways to send metrics to Datadog:
You can also use one of the Datadog official and community contributed API and DogStatsD client libraries to submit your custom metrics
Note: There are no enforced fixed rate limits on custom metric submission. If your default allotment is exceeded, you are billed according to Datadog’s billing policy for custom metrics.