Skip to content

Document socket activation behavior in APM connection errors page #37413

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pgimalac merged 7 commits into from
Jun 12, 2026
Merged

Document socket activation behavior in APM connection errors page #37413

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
66bb2da
[APM] Document socket activation behavior in connection errors troubl…
pgimalac Jun 10, 2026
069be15
Merge branch 'master' into pgimalac/socket-activation-doc
pgimalac Jun 10, 2026
2adae28
Update content/en/tracing/troubleshooting/connection_errors.md
pgimalac Jun 11, 2026
325a6b9
Update content/en/tracing/troubleshooting/connection_errors.md
pgimalac Jun 11, 2026
764618e
fix: review comments
pgimalac Jun 11, 2026
9e7e6f1
Merge branch 'pgimalac/socket-activation-doc' of github.com:DataDog/d…
pgimalac Jun 11, 2026
ab2a743
Apply suggestion from @domalessi
domalessi Jun 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion content/en/tracing/troubleshooting/connection_errors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,6 +171,8 @@ APM Agent
Status: Not running or unreachable on localhost:8126.
```

**Note**: On Linux, starting with Agent 7.80.0, the trace-agent starts only after receiving trace data. This reduces memory usage, but means `agent status` may show APM as not running or unreachable even when APM is correctly configured. If no traces have been sent yet, this is expected behavior. To disable this behavior, set `apm_config.socket_activation.enabled: false` in `datadog.yaml`, or set `DD_APM_SOCKET_ACTIVATION_ENABLED=false` in your environment.

## Troubleshooting the connection problem
Whether it's the SDK or the Datadog Agent displaying the error, there are a few ways to troubleshoot.

Expand Down Expand Up @@ -235,6 +237,8 @@ If your setup is not on Fargate, you can `exec` into the Datadog Agent container

Look for the APM Agent section to confirm whether it is running:

**Note:** On Linux, starting with Agent 7.80.0, the trace-agent starts only after receiving trace data. This reduces memory usage, but means the APM Agent section may show as not running or unreachable even when APM is correctly configured. If no traces have been sent yet, this is expected behavior. To disable this behavior, set `apm_config.socket_activation.enabled: false` in `datadog.yaml`, or set `DD_APM_SOCKET_ACTIVATION_ENABLED=false` in your environment.

```text
=========
APM Agent
Expand Down Expand Up @@ -282,4 +286,4 @@ If the configuration is correct, but you're still seeing connection errors, [con
[18]: /tracing/trace_collection/dd_libraries/php/?tab=containers#apache
[19]: /tracing/trace_collection/dd_libraries/php/?tab=containers#nginx
[20]: /agent/troubleshooting/send_a_flare/?tab=agentv6v7#trace-agent
[21]: https://kubernetes.io/docs/concepts/services-networking/network-policies/
[21]: https://kubernetes.io/docs/concepts/services-networking/network-policies/
Loading