Open xdu-opendoor opened 2 years ago
👋 Thanks for the detailed repro and instructions, it made it really easy to work with it! I think duxing/datadog-otlp/pull/1 will solve your issue (or at the very least it will make OTLP traces reach the Datadog Agent)
@mx-psi I don't think this PR will fix the issue. The issue is inside the datadog-agent and this change opens a port between datadog agent and host machine. and I've verified the change doesn't fix the problem: datadog backend still has no data and tcpdump
on port 5003 (inside datadog-agent
container )still see no traffic.
note this issue persists when I used the latest version 7.35.1
I replied on the PR with detailed steps of what I did, could you take a look?
I replied on the PR with detailed steps of what I did, could you take a look?
checked. sry about duplicating our conversation. let's try to resolve it there and post the result here.
Output of the info page (if this is a bug)
output from
agent status
:output from
trace-agent -info
:Describe what happened:
knowing
opentelemetry-exporter-datadog
is being deprecated, I'm configured my application to useopentelemetry-exporter-otlp
and hopingdatadog-agent
otlp
ingestion feature can make this work.after I made the change, I didn't see the traces going to the APM backend.
Describe what you expected:
using
opentelemetry-exporter-otlp
anddatadog-agent@v7.35.0
, traces from my application show up in datadog backend correctly as before (integrated withopentelemetry-exporter-datadog
)Steps to reproduce the issue:
I've build a project with a simplified app and my configuration: https://github.com/duxing/datadog-otlp all the detailed steps in README.
Additional environment details (Operating System, Cloud provider, etc):
docker
:Docker version 20.10.10, build b485636
docker-compose
:docker-compose version 1.29.2, build 5becea4c