Skip to content
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.

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

[BUG]: Wrong error when no connection to APM socket is possible #174

Open
cmitz opened this issue Feb 24, 2025 · 0 comments
Open

[BUG]: Wrong error when no connection to APM socket is possible #174

cmitz opened this issue Feb 24, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@cmitz
Copy link

cmitz commented Feb 24, 2025

Module Version(s)

1.5.0

Bug Report

Our nginx container runs with the Datadog APM socket file mounted as volume. It is also explicitly configured to use these. However, the container still logs this when it cannot connect to that socket.

2025/02/20 16:08:26 [error] 94#96: nginx-datadog: [error code 4] Error occurred during HTTP request for Remote Configuration: Error sending request with libcurl (Couldn't connect to server): Failed to connect to localhost port 80 after 0 ms: Couldn't connect to server

The expected behaviour is that it logs it can't communicate over that socket, instead of saying it cannot connect to localhost port 80

Reproduction Code

No response

Error Logs

No response

Operating System

No response

@cmitz cmitz added the bug Something isn't working label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant