You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support setting the Ddsource field on the datadogV2.HTTPLogItem struct. The Datadog Send Logs API expects the Ddsource field to be set in order for log items to have a source.
Currently, the transform function sets the Ddtags, Hostname, Message, Service, and AdditionalProperties fields on the datadogV2.HTTPLogItem struct but it does not set the Ddsource field.
functransform(lr plog.LogRecord, host, servicestring, res pcommon.Resource, logger*zap.Logger) datadogV2.HTTPLogItem {
The workaround right now is to use the undocumented ddtags attribute to set the source tag. Thankfully I was able to find this undocumented attribute in open-telemetry/opentelemetry-collector-contrib#15387 (comment). Here's the transform processor that does that.
However, even with this configuration the log event will end up with two source tags, one with the value defined in the ddtags and the other with the value undefined. I suspect the undefined value is due to the API request not setting the Ddsource field which is why I opened this issue. Here's what one would see in the Datadog user interface with the above workaround configuration.
Please let me know what other information is needed from me. Thank you!
The text was updated successfully, but these errors were encountered:
Support setting the
Ddsource
field on thedatadogV2.HTTPLogItem
struct. The Datadog Send Logs API expects theDdsource
field to be set in order for log items to have a source.Currently, the
transform
function sets theDdtags
,Hostname
,Message
,Service
, andAdditionalProperties
fields on thedatadogV2.HTTPLogItem
struct but it does not set theDdsource
field.opentelemetry-mapping-go/pkg/otlp/logs/transform.go
Line 71 in 6e80d7e
The workaround right now is to use the undocumented
ddtags
attribute to set thesource
tag. Thankfully I was able to find this undocumented attribute in open-telemetry/opentelemetry-collector-contrib#15387 (comment). Here's thetransform
processor that does that.However, even with this configuration the log event will end up with two
source
tags, one with the value defined in theddtags
and the other with the valueundefined
. I suspect theundefined
value is due to the API request not setting theDdsource
field which is why I opened this issue. Here's what one would see in the Datadog user interface with the above workaround configuration.Please let me know what other information is needed from me. Thank you!
The text was updated successfully, but these errors were encountered: