- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
View an individual trace to see all of its spans and associated metadata. Each trace can be visualized as either a Flame Graph, Span List, Waterfall, or Map.
The trace header displays critical trace information, including the root span’s service name, resource name, trace ID, end-to-end trace duration, and the trace start time. To get a permalink to the trace, click Open Full Page and save the URL.
The Flame Graph is the default visualization that displays all the color-coded spans from a trace on a timeline. This is useful for understanding the execution path of a request and where time was spent over a trace.
To navigate the graph, scroll to zoom, click and drag to move around, and use the minimap to zoom into the selected span or zoom out to the full trace.
The legend details the color coding of the flame graph. Group spans by either Service (default), Base service (service from which the span is emitted), Host, or Container. Choose to display either the percentage of trace execution time (% Exec Time) or span count (Spans) by group. If errors exist on spans in the trace, highlight them in the flame graph by selecting the Errors checkbox under Filter Spans.
Spans from inferred services are represented with a dashed outline.
Displays resources by group (service by default) and sorts them according to their count of spans. This visualization is useful for scanning latency information by resource or grouping.
Filter resources by type or naming information using the corresponding buttons and text-based search.
Groups can be sorted by clicking on the corresponding column header: RESOURCE, SPANS, average duration (AVG DURATION), execution time (EXEC TIME), or percentage of trace execution time (% EXEC TIME).
Displays all spans for a trace on a timeline where each row corresponds to a span. This visualization is useful for isolating and focusing on relevant parts of a trace.
Each row (span) indicates the following:
Spans from inferred services are represented with a dashed underline.
To expand or collapse span descendants, click the chevron (>) icon on a row. To expand or collapse all spans, click the Expand all (+) or Collapse all (-) buttons.
Trace map displays a representation of all services involved in a single trace. It provides an overview of the transaction lifecycle at the service level and shows service dependencies.
Each node on the map represents a service in the transaction lifecycle. To prevent cyclic dependencies on the map, services that call another service that had already been invoked by the original service, are represented by duplicated nodes. Inferred services are represented with a dashed outline and a purple background.
Service nodes explicitly show the percentage of the total execution time, which shows the trace duration breakdown at the service level.
If a service entry span is in an error state, the corresponding service node is marked with a red border to highlight a faulty services. If an error occurs in a service exit span, the edge indicating the call to the next service is also highlighted in red.
To view additional information about the service entry spans for each node, hover over the error state. The tooltip displays details about the service entry span’s operation and resource name, along with any error messages. To further investigation, click View Entry Span to switch to the Waterfall view.
In the Waterfall and Flamegraph visualizations, the search option allows you to find the spans that meet specific queries. Spans that match the search query are highlighted in the trace view and you can navigate between these matches using the arrows next to the search bar.
Note: When the Error
checkbox is selected, the search results return spans that match the query and are in an error state.
The search query on the trace side panel supports the following options:
web
service:web-ui
Note: Wildcards are not supported in the Trace search bar.
Supported expressions:
language:(go OR python)
service:event-query OR terminator
duration:>200ms
Note: Numerical values support <
, >
, <=
, and >=
expressions.
The height-adjustable bottom of the Trace View shows selected span and trace information.
The span header contains service, operation, and resource names of the selected span as well as latency information. Pivot to other parts of the platform or narrow down your Trace Explorer search by clicking on the naming pill.
When the span represents a client call from an instrumented service to a database, a queue, or a third-party service, the span header shows the service and the inferred entity.
See all span metadata, including custom tags. Click on a span tag to update the search query in the Trace Explorer or copy the tag’s value to the clipboard.
Other information may be displayed under various conditions:
Error message and stack trace (on error span)
SQL Query markup (on database spans)
RUM Context and Metadata (on RUM spans)
Spark Metrics (on Spark job spans)
A git warning message (when git information is missing on a CI Test)
When the service name is an override from the base service name, the top of the info section shows the:
Base service: service from which the span is emitted, identified by the @base_service
attribute.
Service override: service name, different from the base service name, set automatically in Datadog integrations or changed via the programmatic API. The service override is identified by the service
reserved attribute.
Inferred service (when applicable): name of the inferred entity being called by the base service, identified by one of the peer attributes.
Toggle between host-level and container-level (when available) infrastructure information for the selected span.
See associated tags, as well as critical host/container metrics graphs including CPU, Memory, and I/O with an overlay of when the trace occurred.
See logs related to your service at the time of the trace. When you hover over a log, a line showing its timestamp is displayed on the trace flame graph. Clicking on the log brings you to the Log Explorer search.
Click on a service’s span to see the processes running on its underlying infrastructure. A service’s span processes are correlated with the hosts or pods on which the service runs at the time of the request. You can analyze process metrics such as CPU and RSS memory alongside code-level errors to distinguish between application-specific and wider infrastructure issues. Clicking on a process will bring you to the Live Processes page. To view span-specific processes, enable process collection. Related processes are not currently supported for serverless and browser traces.
Click on a service’s span to see network dependencies of the service making the request. Use key network performance metrics such as volume, errors (TCP retransmits), and network latency (TCP round-trip time) to differentiate between application-specific and network-wide issues, especially when no code errors have been generated. For instance, you can use network telemetry to determine if high request latency is due to traffic overloading of the relevant application, or faulty dependencies with a downstream pod, security group, or any other tagged endpoint. Clicking on a process brings you to the Network Analytics page. To view span-specific processes, enable Cloud Network Monitoring.
Note: Related network telemetry is not currently supported for serverless traces.
See attack attempts that target the services of the distributed trace. You can see the pattern used by the attacker, the rule that detects the attack, and whether the attacker found a vulnerability in your service.
Click View in ASM to investigate further using Datadog Application Security Management.
View Profiles to identify lines of code related to performance issues. The values on the left side represent the time spent in each method call during the selected span.
Span links correlate one or more spans together that are causally related but don’t have a typical parent-child relationship.
Click a span in the flame graph to display spans connected with span links:
Note: Span links only display when the corresponding spans are ingested and indexed, for example, with a retention filter.
To learn more about span links and how to add them with custom instrumentation, read Span Links.
추가 유용한 문서, 링크 및 기사: