Component(s)
receiver/otlp
What happened?
Describe the bug
The profiles OTLP receiver calls StartTracesOp / EndTracesOp instead of StartProfilesOp / EndProfilesOp, causing all received profile samples to be reported as trace spans in observability metrics.
What did you expect to see?
Profile samples reported under profiles receiver metrics.
What did you see instead?
More traces than we expected to see, without any profiles-specific metrics emitted.
Collector version
d686cf9
Environment information
No response
OpenTelemetry Collector configuration
receivers:
otlp:
protocols:
http:
endpoint: 0.0.0.0:4318
grpc:
endpoint: 0.0.0.0:4317
processors:
batch:
timeout: 10s
exporters:
debug:
verbosity: detailed
prometheus:
endpoint: 0.0.0.0:9999
service:
pipelines:
metrics:
receivers: [otlp]
processors: [batch]
exporters: [prometheus]
traces:
receivers: [otlp]
processors: [batch]
exporters: [debug]
logs:
receivers: [otlp]
processors: [batch]
exporters: [debug]
profiles:
receivers: [otlp]
exporters: [debug]
Log output
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Component(s)
receiver/otlp
What happened?
Describe the bug
The profiles OTLP receiver calls
StartTracesOp/EndTracesOpinstead ofStartProfilesOp/EndProfilesOp, causing all received profile samples to be reported as trace spans in observability metrics.What did you expect to see?
Profile samples reported under profiles receiver metrics.
What did you see instead?
More traces than we expected to see, without any profiles-specific metrics emitted.
Collector version
d686cf9
Environment information
No response
OpenTelemetry Collector configuration
Log output
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.