Source
APM, tracing & profiling — found from sitemap — Datadog APM & Error Tracking
Checked for Datadog APM & Error Tracking on 6 Nov 2026
- Page
- https://docs.datadoghq.com/profiler/connect_traces_and_profiles/
- Checked
- 6 Nov 2026, 04:29 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:09ed7e74536c0c4cd5190e27aed7bb05fcae3d083cbb8fa6d4108998c81c9382
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Trace profile auto linking Report an error
“Application processes that have both APM distributed tracing and continuous profiler enabled are automatically linked.”
-
Java default trace profiling Report an error
“The Trace to Profiling integration is enabled by default when you turn on profiling for your Java service on Linux and macOS. The feature is not available on Windows.”
-
Java manual scope activation Report an error
“For manually instrumented code, continuous profiler requires scope activation of spans”
-
Span timeline view Report an error
“The timeline view surfaces time-based patterns and work distribution over the period of the span. It provides a visual breakdown of how threads contributed to the request over time.”
-
Timeline automated analysis Report an error
“Use Automated Analysis to highlight performance issues directly in the view, such as oversized thread pools or GC contention”
-
Profile from trace flamegraph Report an error
“From the timeline, click Open in Profiling to see the same data on a new page. From there, you can change the visualization to a flame graph.”
-
Profile scope options Report an error
“Span & Children scopes the profiling data to the selected span and all descendant spans in the same service.”
-
Full profile scope duration Report an error
“Full profile scopes the data to 60 seconds of the whole service process that executed the previously selected span.”
-
Endpoint profiling Report an error
“Endpoint profiling allows you to scope your flame graphs by any endpoint of your web service to find endpoints that are slow, latency-heavy, and causing poor end-user experience.”
-
Endpoint profiling java default Report an error
“Endpoint profiling is enabled by default when you turn on profiling for your Java service. Requires using the Datadog profiler. JFR is not supported.”
-
Java recommend datadog profiler Report an error
“It's highly recommended to use the Datadog profiler instead of Java Flight Recorder (JFR).”
-
Service page profiling tab Report an error
“In the APM Service page, use the information in the Profiling tab to correlate a latency or throughput change to a code performance change.”
-
Endpoint resource tracking Report an error
“It is valuable to track top endpoints that are consuming valuable resources such as CPU and wall time.”
-
Per endpoint call view Report an error
“Select Per endpoint call to see behavior changes even as traffic shifts over time.”
-
Timeline thread lanes Report an error
“Each lane represents a thread. Threads from a common pool are grouped together.”
-
Endpoint profiling language support Report an error
“Java Python Go Ruby Node.js .NET PHP”
Scores citing this record
- The Agency Tech Lead APM, tracing & profiling
- The Data Protection Officer APM, tracing & profiling
- The Mobile Team Lead APM, tracing & profiling
- The SaaS CTO APM, tracing & profiling
- The Skeptic APM, tracing & profiling
- The Site Reliability Engineer APM, tracing & profiling