Datadog automatically generates a set of standard metrics from APM trace data. For measuring latency, it creates distribution metrics. The naming convention for these metrics is trace.. A distribution metric captures statistical information about a set of values, including count, min, max, average, and various percentiles (p50, p75, p99), which collectively represent the latency distribution. Therefore, trace.graphql.execute is the specific distribution metric that represents the latency for all spans named graphql.execute.

A. trace.graphql.execute.apdex is a metric representing the Apdex score, a measure of user satisfaction, not the raw latency distribution.

B. trace.graphql.execute.hits is a count metric that represents the total number of graphql.execute spans, indicating throughput, not latency.

C. trace.graphql.execute.spancount is not a standard suffix for default APM metrics; the correct suffix for a count is .hits.

E. The .distribution suffix is not part of the standard naming convention for these default metrics; the base name trace. itself represents the distribution metric.

1. Datadog Documentation, "APM Metrics". This page lists the standard metrics generated from traces, confirming that trace. is a distribution metric type that tracks the timing of spans.

2. Datadog Documentation, "Metrics Types". This page describes the "Distribution" metric type, explaining that it is used to track the statistical distribution of a set of values, which is ideal for latency measurements.