Closed yujianweilai closed 2 months ago
Wasn't I clear enough? No, we don't support that.
You are referring to otel docs, that is not our landscapes. otel community maintains that. Reach then if you need.
Wasn't I clear enough? No, we don't support that.
got it , sorry i should not submit this issue in skywalking github.
Search before asking
Apache SkyWalking Component
Java Agent (apache/skywalking-java)
What happened
My situation: Previously, we used skywalking-agent to transport trace data to skywalking-server. Now I used otel-collector + jaeger instead of skywalking-server. I hope that the skywalking-agent send the tracing data to otel-collector, and then otel-collector forwards it to jaeger for storage and display. The problem is that the tracing data cannot be passed to otel-collector. My configuration: /otel-collector/ /skywalking-agent config/ [root@cx-gateway-service-4100-6b6bdd45cc-pvj98 /]# env|grep SW SW_LOGGING_DIR=/var/log/cx-gateway-service SW_AGENT_NAME=cx-gateway-service SW_AGENT_COLLECTOR_BACKEND_SERVICES=10.100.220.63:11800 # IP 10.100.220.63 is one of otel-collector node address SW_LOGGING_MAX_HISTORY_FILES=50
Software Version: skywalking-agent: 8.0.1 otel-collector: 0.85.0
What you expected to happen
According to the official documentation(https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/v0.85.0/receiver/skywalkingreceiver/README.md), when OTEL interconnects with Skywalking, there are few configuration steps. I don't know what steps I'm missing ? Expect help from experts ,Thanks
How to reproduce
none
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Code of Conduct