- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
A resource is a particular action for a given service (typically an individual endpoint or query). Read more about resources in Getting Started with APM. For each resource, APM automatically generates a dashboard page covering:
Datadog provides out-of-the-box graphs for any given resource:
Requests - Choose to display:
Latency - Choose to display:
Error - Choose to display:
Sub-Services: When there are multiple services involved, a fourth graph is available that breaks down your Total time spent/%of time spent/Avg time per request of your service by services or type.
This represents the total/relative/average time spent by traces from the current service to the other services or type.
Note: For services like Postgres or Redis, which are “final” operations that do not call other services, there is no sub-services graph.
On the upper-right corner of each graph, click on the up arrow in order to export your graph into a pre-existing Dashboard.
The resource page also displays a resource latency distribution graph:
Use the top right percentile selectors to zoom into a given percentile, or hover over the sidebar to view percentile markers.
You can also view a map of all of a resource’s upstream and downstream service dependencies. With the Dependency Map Navigator, you can see the flow of services, with spans that go through a specific resource ( endpoint, database query, etc.) end-to-end, along with their request counts.
This map is based on a sample of ingested spans; the sample is drawn by a fixed sampling algorithm that considers the structure of traces. The sampling algorithm is not configurable and is not impacted by ingestion control.
The dependency map is only available for resources containing service entry spans.
Hover over a node to view metrics of each service including requests/second, error rate, and average latency. Click on a node to open a context menu with options to view the Service Page, related traces, and more.
The highlight color of the node indicates the service’s monitor status. If a service has more than one configured monitor, the status of the most severe monitor is shown.
A service has load amplification if it’s receiving more than 100% of the requests received by the selected resource upstream. Services with call paths highlighted in orange have load amplification, and the amplification multiplier is shown in the list on the panel. The amplification is calculated based on the requests received by the resource (shown highlighted on the map in the image below), and the requests received by the downstream service (shown inside the downstream service node on the map). By clicking on a service in the list, you can see the spans contributing to the amplification.
For a given resource, Datadog provides you a span analysis breakdown of all matching traces:
The displayed metrics represent, per span:
Avg Spans/trace
% of Traces
Avg Duration
Avg % Exec Time
Note: A span is considered active when it’s not waiting for a child span to complete. The active spans at a given time, for a given trace, are all the leaf spans (in other words, spans without children).
The span summary table is only available for resources containing service entry spans.
Consult the list of traces associated with this resource in the Trace search modal already filtered on your environment, service, operation, and resource name:
Additional helpful documentation, links, and articles: