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:
- Key health metrics
- Monitor status for all monitors associated with this service
- List of metrics for all resources associated with this service
Out-of-the-box graphs
Datadog provides out-of-the-box graphs for any given resource. Use the dropdown above each graph to change the displayed information.
Requests and Errors
The Requests and Errors graph displays the total number of requests (hits) and errors over time. Using the dropdown menu, you can also view:
- Requests by Version: Breakdown of requests across different service versions.
- Requests per Second by Version: The rate of requests for each version.
- Requests and Errors Per Second: The rate of requests (hits) and errors per second.
Errors
The Errors graph displays the total count of errors over time. Using the dropdown menu, you can also view:
- Errors by Version: The error counts for each service version side by side.
- Errors per Second by Version: The error rate (errors per second) for each service version over time.
- Errors per Second: The overall error rate for the service, per second.
- % Error Rate by Version: The percentage of requests resulting in errors for each service version.
- % Error Rate: The overall error rate for the service, as a percentage.
Latency
The Latency graph displays the latency percentiles as a timeseries. Using the dropdown menu, you can also view:
- Latency by Version: Latency broken down by service version.
- Historical Latency: Comparison of the current latency distribution with the previous day and week.
- Latency Distribution: The distribution of latencies over the selected time frame.
- Latency by Error: The latency of requests over time, segmented by whether the requests resulted in errors.
- Apdex (Application Performance Index): The Apdex score over time.
Avg Time per Request
For services involving multiple downstream services, a fourth graph breaks down the average execution time spent per request. This graph is built on sampled trace data, unlike the other top graphs which use unsampled data sources.
Using the dropdown menu, you can also view:
- Total Time Spent: The cumulative time spent in each downstream service over time.
- % of Time Spent: The percentage of time spent in each downstream service relative to the total time.
For services like Postgres or Redis, which are final operations that do not call other services, there is no sub-services graph. Watchdog performs automatic anomaly detection on the Requests, Latency, and Error graphs. If an anomaly is detected, an overlay appears on the graph. Clicking the Watchdog icon provides more details in a side panel.
Export to dashboard
On the upper-right corner of each graph, click on the up arrow in order to export your graph into a pre-existing Dashboard.
Latency distribution
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.
Dependency Map
Use the Dependency Map to view a flow graph of all of a resource’s upstream and downstream service dependencies. The map is scoped to the requests flowing through the selected service and resource (endpoint, database query, etc.) you’re focused on.
Click on a downstream or upstream service node to see which resources are invoked in the request flow. To focus on a particular request path, select a node an click set as start/end. This filters the map to focus on the requests that also flow through this upstream or downstream dependency.
Note: This map is based on a sample of ingested spans. Request rates are then upscaled based on applied sampling rates to represent actual application/service traffic.
The dependency map is only available for service-entry span resources.
Note: Service overrides are represented as part of the edge of the dependency map to keep visibility over the actual remote service, database or queue the service is interacting with.
Frontend Impact
Datadog provides you visibility into how a web resource impacts your frontend applications. You can understand what frontend view is sending requests to the resource and identify views that are experiencing high latency or errors from the resource.
Isolate requests and errors over time for a specific frontend view by hovering over a RUM View Name in the table and clicking on Isolate this View. From here, you can explore sampled traces originating from the frontend views by clicking on View Traces at the top right of the panel. You can also investigate the sampled RUM sessions for each view by clicking on the context menu for a frontend view in the table.
The frontend impact panel is only available if you use Real User Monitoring (RUM) and the resource belongs to a web service. Unlike the requests, errors, and latency graphs which use unsampled data sources, the frontend impact metrics are built on sampled trace data from the past 1 hour:
RUM View Name:- Name of the frontend view
App Name:- Name of application that contains the frontend view
Sessions:- Number of sessions for the frontend view
Error Rate Per Sessions:- Number of sessions that included the frontend view
P95 Latency- P95 latency for requests originating from the frontend view
Requests- Number of requests originating from the frontend view
Span summary
For a given resource, Datadog provides you a span analysis breakdown of all matching traces:
The displayed metrics represent, per span:
Avg Spans/trace- Average number of occurrences of the span, for traces including the current resource, where the span is present at least once.
% of Traces- Percentage of traces including the current resource where the span is present at least once.
Avg Duration- Average duration of the span, for traces including the current resource, where the span is present at least once.
Avg % Exec Time- Average ratio of execution time for which the span was active, for traces including the current resource, where the span is present at least once.
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.
Traces
Consult the list of traces associated with this resource in the Trace search modal already filtered on your environment, service, operation, and resource name:
Further Reading
Additional helpful documentation, links, and articles:
