-
Notifications
You must be signed in to change notification settings - Fork 51
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
Cannot use CI Visibility with DogStatsD over Unix Domain Socket #283
Comments
Thanks @usmonster for reporting the issue. After investigating a bit, I can confirm that Unix Domain Sockets are not supported for sending CI Visibility traces. I updated our docs with this limitation and we will work on adding support for this in a near future. |
Thanks for your contribution! This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community. If you would like this issue to remain open:
|
Hello! I can confirm that the issue is reproducible even after upgrading the plugin to the latest version 4.0.0. (Details remain the same.) Thanks! |
Hello again! Can the stale label please be removed? Thanks! |
I'm using the Datadog plugin on Jenkins with the Datadog Agent and a Unix socket configuration.
This is working fine for metrics reporting, but not for CI Visibility/traces. Looking at Jenkins logs during a pipeline run, I see the plugin is trying to use HTTP instead of the configured DSD, and so it fails (screenshot further below).
I've tried looking at the plugin source code and found no clue, so I'm wondering if there's something I'm missing, but I suspect it's a bug, i.e. that the plugin was not designed with the unix socket configuration in mind (cf. #242). Thanks for any insights you might have!
To Reproduce
Steps to reproduce the behavior:
0
), and save the configurationExpected behavior
The plugin should use the DSD configuration (not HTTP), traces should be sent without error, and Jenkins build data should show up in Datadog's Pipeline Visibility feature.
Screenshots
Here's how the plugin configuration looks in Jenkins:
(Note that I have to set
0
for the Traces Collection Port to enable CI Visibility; the "Test traces connection" button fails, but maybe this is expected behavior in this case? I can still save the configuration.)Here is the Jenkins logger configuration:
Here are the logs that show the error:
Environment and Versions:
Additional context
Jenkins Logs
Here are the same logs as in the previous screenshot (included as text for searches):
The text was updated successfully, but these errors were encountered: