ysj2018 opened a new issue, #13729: URL: https://github.com/apache/skywalking/issues/13729
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues. ### Apache SkyWalking Component OAP server (apache/skywalking) ### What happened I am using SkyWalking version 10.3 and intend to use it as a server to receive OpenTelemetry data. I am using opentelemetry-collector 0.115 to send data (metrics, logs, traces) to SkyWalking, but it keeps failing (neither gRPC nor HTTP protocols work). error message: 2026-03-06T13:28:13.015+0800 error internal/queue_sender.go:100 Exporting failed. Dropping data. {"kind": "exporter", "data_type": "traces", "name": "otlp/skywalking", "error": "not retryable error: Permanent error: rpc error: code = Unimplemented desc = Method not found: opentelemetry.proto.collector.trace.v1.TraceService/Export", "dropped_items": 8} go.opentelemetry.io/collector/exporter/exporterhelper/internal.NewQueueSender.func1 go.opentelemetry.io/collector/[email protected]/exporterhelper/internal/queue_sender.go:100 go.opentelemetry.io/collector/exporter/internal/queue.(*Consumers[...]).Start.func1 go.opentelemetry.io/collector/[email protected]/internal/queue/consumers.go:43 2026-03-06T13:28:18.007+0800 info Traces {"kind": "exporter", "data_type": "traces", "name": "debug", "resource spans": 1, "spans": 4} 2026-03-06T13:28:18.009+0800 error internal/queue_sender.go:100 Exporting failed. Dropping data. {"kind": "exporter", "data_type": "traces", "name": "otlp/skywalking", "error": "not retryable error: Permanent error: rpc error: code = Unimplemented desc = Method not found: opentelemetry.proto.collector.trace.v1.TraceService/Export", "dropped_items": 4} go.opentelemetry.io/collector/exporter/exporterhelper/internal.NewQueueSender.func1 go.opentelemetry.io/collector/[email protected]/exporterhelper/internal/queue_sender.go:100 go.opentelemetry.io/collector/exporter/internal/queue.(*Consumers[...]).Start.func1 go.opentelemetry.io/collector/[email protected]/internal/queue/consumers.go:43 2026-03-06T13:28:23.008+0800 info Traces {"kind": "exporter", "data_type": "traces", "name": "debug", "resource spans": 1, "spans": 5} my opentelemetry-collector config : receivers: otlp: protocols: grpc: endpoint: 0.0.0.0:8337 http: endpoint: 0.0.0.0:8338 processors: batch: send_batch_size: 100 timeout: 5s resource: attributes: - key: service.name value: "otel-apmcoretest" action: upsert exporters: # New OTLP HTTP configuration with only core settings retained otlp: endpoint: "http://10.251.21.91:11800"; tls: insecure: true # Use debug instead of logging in the new version debug: verbosity: basic service: pipelines: traces: receivers: [otlp] processors: [batch, resource] exporters: [otlp, debug] metrics: receivers: [otlp] processors: [batch, resource] exporters: [otlp, debug] Does SkyWalking 10.3 not support receiving OpenTelemetry data in this way? Or is there an issue with my configuration? ### What you expected to happen I want my OpenTelemetry data to be reported to the SkyWalking server via the OpenTelemetry Collector, and to be viewable in the SkyWalking UI. Please help me figure out how to do this. ### How to reproduce I have provided my configuration in the problem description, and the issue can be reproduced using this configuration. I am using the official binary packages directly for both SkyWalking 10.3 and the Collector. ### Anything else I have tried sending metrics, logs, and traces, as well as sending only one type of data at a time, but none of them worked. I also tried different versions of the Collector: 0.122, 0.115, and 0.85. ### Are you willing to submit a pull request to fix on your own? - [x] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
