[Bug] opentelemetry.proto.collector.trace.v1.TraceService/Export

[ysj2018]

Search before asking

• I had searched in the issues 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/exporter@v0.115.0/exporterhelper/internal/queue_sender.go:100
go.opentelemetry.io/collector/exporter/internal/queue.(*Consumers[...]).Start.func1
go.opentelemetry.io/collector/exporter@v0.115.0/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/exporter@v0.115.0/exporterhelper/internal/queue_sender.go:100
go.opentelemetry.io/collector/exporter/internal/queue.(*Consumers[...]).Start.func1
go.opentelemetry.io/collector/exporter@v0.115.0/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?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

You didn't add title. I had to add that for you.
You didn't read docs, actually, you should activate the zipkin-handler manually, we only made metrics/logs activated by default.

https://skywalking.apache.org/docs/main/latest/en/setup/backend/otlp-trace/

[wu-sheng]

This has been moved into the default configuration in #13731. The otlp-traces handler is now activated by default in receiver-otel.