This page is not yet available in Spanish. We are working on its translation. If you have any questions or feedback about our current translation project, feel free to reach out to us!
This check collects profiles from Go applications which expose the /debug/pprof endpoint.
NOTE: Prefer instrumenting services with the dd-trace-go profiling client library. The client library
offers better integration with other Datadog services, such as through code hotspots and endpoint filtering.
Use this integration for services for which you do not control the source code.
NOTE: Using this integration results in billing for hosts under Datadog’s Continuous Profiler service.
For more on Continuous Profiler billing, consult our billing documentation.
Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.
Edit the go_pprof_scraper.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your Go performance data. See the sample go_pprof_scraper.d/conf.yaml for all available configuration options.
go_pprof_scraper.can_connect Returns CRITICAL if the check cannot reach the pprof endpoint or if APM is not enabled, returns OK otherwise. Statuses: ok, critical
