- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
Tracing application metrics are collected after you enable trace collection and instrument your application.
These metrics capture request counts, error counts, and latency measures. They are calculated based on 100% of the application’s traffic, regardless of any trace ingestion sampling configuration. Ensure that you have full visibility into your application’s traffic by using these metrics to spot potential errors on a service or a resource, and by creating dashboards, monitors, and SLOs.
Note: If your applications and services are instrumented with OpenTelemetry libraries and you set up sampling at the SDK level and/or at the collector level, APM metrics are calculated based on the sampled set of data.
Trace metrics are generated for service entry spans and certain operations depending on integration language. For example, the Django integration produces trace metrics from spans that represent various operations (1 root span for the Django request, 1 for each middleware, and 1 for the view).
The trace metrics namespace is formatted as:
trace.<SPAN_NAME>.<METRIC_SUFFIX>
With the following definitions:
<SPAN_NAME>
span.name
(examples: redis.command
, pylons.request
, rails.request
, mysql.query
).<METRIC_SUFFIX>
hits
, errors
, apdex
, duration
). See the section below.<TAGS>
env
, service
, version
, resource
, http.status_code
, http.status_class
, and Datadog Agent tags (including the host and second primary tag).
Note: Other tags set on spans are not available as tags on traces metrics.trace.<SPAN_NAME>.hits
redis.command
, pylons.request
, rails.request
, or mysql.query
).env
, service
, version
, resource
, resource_name
, http.status_code
, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.hits.by_http_status
env
, service
, version
, resource
, resource_name
, http.status_class
, http.status_code
, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>
env
, service
,version
, resource
, resource_name
, http.status_code
, synthetics
, and the second primary tag.trace.<SPAN_NAME>.errors
env
, service
, version
, resource
, resource_name
, http.status_code
, all host tags from the Datadog Host Agent, and the second primary tag.trace.<SPAN_NAME>.errors.by_http_status
env
, 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>.apdex
env
, service
, version
, resource
/ resource_name
, synthetics
, and the second primary tag.trace.<SPAN_NAME>.duration
sum:trace.<SPAN_NAME>.duration{<FILTER>}.rollup(sum).fill(zero) / sum:trace.<SPAN_NAME>.hits{<FILTER>}
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_status
env
, service
, resource
, http.status_class
, http.status_code
, all host tags from the Datadog Host Agent, and the second primary tag.Additional helpful documentation, links, and articles: