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
According to the OpenTelemetry documentation, for example the resource.attributes.cloud should contain keys that are separted by a dot, instead of the @ sign.
Instead they seem to be replaced here.
Is there a reason, that the keys under resource.attributes and log.attributes are separated with @ instead of being kept in its original (Otel) format?
The text was updated successfully, but these errors were encountered:
This "dedotting" is necessary because OpenSearch interprets dots in field names as nested JSON objects. I wrote a longer explanation of this in #4977. This process helps avoiding field type conflicts during indexing.
Currently a log message in dataprepper looks like this, after being ingested via the otel-logs-source:
The log itself was collected via otel/reciever/filelog.
According to the OpenTelemetry documentation, for example the resource.attributes.cloud should contain keys that are separted by a dot, instead of the
@
sign.Instead they seem to be replaced here.
Is there a reason, that the keys under
resource.attributes
andlog.attributes
are separated with@
instead of being kept in its original (Otel) format?The text was updated successfully, but these errors were encountered: