Automatic configuration

To enable Go runtime metrics collection, start the tracer using the WithRuntimeMetrics option:

tracer.Start(tracer.WithRuntimeMetrics())

View runtime metrics in correlation with your Go services on the Service Catalog in Datadog.

By default, runtime metrics from your application are sent every 10 seconds to the Datadog Agent with DogStatsD. Make sure that DogStatsD is enabled for the Agent. If your Datadog Agent DogStatsD address differs from the default localhost:8125, use the WithDogstatsdAddress option (available starting in 1.18.0) or the environment variables DD_AGENT_HOST and DD_DOGSTATSD_PORT.

If WithDogstatsdAddress is not used, the tracer attempts to determine the address of the statsd service according to the following rules:

1. Look for /var/run/datadog/dsd.socket and use it if present. IF NOT, continue to #2.
2. The host is determined by DD_AGENT_HOST, and defaults to “localhost”.
3. The port is retrieved from the Agent. If not present, it is determined by DD_DOGSTATSD_PORT, and defaults to 8125.

If you are running the Agent as a container, ensure that DD_DOGSTATSD_NON_LOCAL_TRAFFIC is set to true, and that port 8125 is open on the Agent. Additionally, for Kubernetes or ECS, follow the guidelines below:

• Kubernetes: You must bind the DogstatsD port to a host port.
• ECS: Set the appropriate flags in your task definition.

Alternatively, the Agent can ingest metrics with a Unix Domain Socket (UDS) as an alternative to UDP transport. For more information, read DogStatsD over Unix Domain Socket.

Data Collected

The following metrics are collected by default after enabling Go metrics.

Along with displaying these metrics in your APM Service Page, Datadog provides a default Go Runtime Dashboard.

Further Reading

Additional helpful documentation, links, and articles:

Connect your Logs and Traces togetherDOCUMENTATION Manually instrument your application to create traces.DOCUMENTATION Explore your services, resources, and tracesDOCUMENTATION