-
Notifications
You must be signed in to change notification settings - Fork 272
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 send traces to Datadog agent #2225
Comments
@col is this still happening? |
Yeah, I never managed to get this working |
alright, let's look more closely at that now that a lot of fixes went into our telemetry stack. A few questions first:
(we have a bit more confidence in the OTLP exporter than in the Datadog one, they come from different libraries) |
@col any updates on this? |
Thanks for the prompt. I have not given this another try yet but I'll get back to it soon.
|
This is fixed in the upgrade to opentelemetry 0.19.0. I verified by creating a k8s cluster, installing the datadog agent and exporting traces to the datadog agent as follows: datadog configuration fragment (as per the official DD helm chart)
router configuration fragment
|
Reopening the issue since we have to revert the upgrade until they release a patch. See #3242 |
Describe the bug
I'm deploying apollo-router using the helm chart (v1.0.0-rc.7) into a k8s cluster. The cluster has the Datadog agent running as a Daemonset and is working as expected for traces coming from the backend services. I've been working on this for days now and I cannot get the traces from apollo-router to appear in Datadog.
To Reproduce
I'm using the following configuration:
Expected behavior
I'm expecting to see trace data in the Datadog console
Output
If applicable, add output to help explain your problem.
Additional context
I've enabled debug logging (
APOLLO_ROUTER_LOG=debug
) but it's not giving me anything particularly useful to debug this issue.The text was updated successfully, but these errors were encountered: