Tracing application metrics are collected after enabling trace collection and instrumenting your application. These metrics are available for dashboards and monitors. The trace metrics namespace is formatted as:
trace.<SPAN_NAME>.<METRIC_SUFFIX>trace.<SPAN_NAME>.<METRIC_SUFFIX>.<2ND_PRIM_TAG>_serviceWith the following definitions:
<SPAN_NAME>span.name (examples: redis.command, pylons.request, rails.request, mysql.query).<METRIC_SUFFIX>duration, hits, span_count). See the section below.<2ND_PRIM_TAG><TAGS>env, service, version, resource, sublayer_type, sublayer_service, http.status_code, http.status_class, Datadog Agent tags (including the host and second primary tag). Note: Tags set on spans do not count and will not be available as tags for your traces metrics.trace.<SPAN_NAME>.hitsenv, service, version, resource, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.hits.by_http_statusenv, service, version, resource, http.status_class, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>env, service, resource, resource_name, version, synthetics, and the second primary tag.trace.<SPAN_NAME>.errorsenv, service, version, resource, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.errors.by_http_statusenv, service, version, resource, http.status_class, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.Note: This is a deprecated namespace.
trace.<SPAN_NAME>.span_countenv, service, resource, all host tags on from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.span_count.by_http_statusenv, service, resource, http.status_class, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.durationtrace.<SPAN_NAME>.duration is divided by trace.<SPAN_NAME>.hits, the result can yield an average latency, but this is not the recommended approach for calculating the average latency. Instead, refer to the Latency Distribution section for average latency calculations.env, service, resource, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.duration.by_http_statusenv, service, resource, http.status_class, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.duration.by_serviceenv, service, resource, sublayer_service, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.duration.by_typeenv, service, resource, sublayer_type, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.duration.by_type.by_http_statusenv, service, resource, sublayer_type, http.status_class, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.duration.by_service.by_http_statusenv, service, resource, sublayer_service, http.status_class, http.status_code, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.apdexenv, service, resource / resource_name, version, synthetics, and the second primary tag.The following legacy apdex metrics are deprecated.
trace.<SPAN_NAME>.apdex.by.resource_<2ND_PRIM_TAG>_serviceenv, service, resource / resource_name, and the second primary tag.trace.<SPAN_NAME>.apdex.by.resource_serviceenv, service, and resource / resource_name.trace.<SPAN_NAME>.apdex.by.<2ND_PRIM_TAG>_serviceenv, service, and the second primary tag.trace.<SPAN_NAME>.apdex.by.serviceenv and service.Additional helpful documentation, links, and articles:
