Closed povilasv closed 10 months ago
receiver/datadogreceiver
Looks like DataDog's library uses ".NET" as value instead of "dotnet" in their instrumentation:
See: https://github.com/DataDog/dd-trace-dotnet/blob/ecb5d5949f6c29dbe99a451c7a3574013cfeb1bd/tracer/src/Datadog.Trace/AgentHttpHeaderNames.cs#L76
So we need to remap ".NET" to "dotnet" to follow OTEL semantic conventions.
I've also doublechecked other variables, and they seem to map to semantic conventions correctly -> https://opentelemetry.io/docs/specs/semconv/resource/#telemetry-sdk
The only other odd language is javascript. DD uses "javascript" in their instrumentation -> https://github.com/search?q=repo%3ADataDog%2Fdd-trace-js%20Datadog-Meta-Lang&type=code
But we don't seem to have equivalent in semantic conventions?
v0.89.0
OS: (e.g., "Ubuntu 20.04") Compiler(if manually compiled): (e.g., "go 14.2")
No response
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
uups wrongly selected receiver , sorry for the ping
Component(s)
receiver/datadogreceiver
What happened?
Description
Looks like DataDog's library uses ".NET" as value instead of "dotnet" in their instrumentation:
See: https://github.com/DataDog/dd-trace-dotnet/blob/ecb5d5949f6c29dbe99a451c7a3574013cfeb1bd/tracer/src/Datadog.Trace/AgentHttpHeaderNames.cs#L76
So we need to remap ".NET" to "dotnet" to follow OTEL semantic conventions.
I've also doublechecked other variables, and they seem to map to semantic conventions correctly -> https://opentelemetry.io/docs/specs/semconv/resource/#telemetry-sdk
The only other odd language is javascript. DD uses "javascript" in their instrumentation -> https://github.com/search?q=repo%3ADataDog%2Fdd-trace-js%20Datadog-Meta-Lang&type=code
But we don't seem to have equivalent in semantic conventions?
Steps to Reproduce
Expected Result
Actual Result
Collector version
v0.89.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response