[exporter/opensearchexporter] Support OLTP Mapping

[felipeweb]

Component(s)

exporter/opensearch

Is your feature request related to a problem? Please describe.

Today the exporter convert the data to one of these mappings [ss4o, ecs, flatten_attributes] but I want to mapping OTLP.

Describe the solution you'd like

Add support to OTLP Mapping

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/opensearch: @Aneurysm9 @MitchellGale @MaxKsyunz @YANG-DB

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[perry-mitchell]

Any guidance here on how to achieve OTLP -> OpenSearch?

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• exporter/opensearch: @Aneurysm9 @MitchellGale @MaxKsyunz @YANG-DB

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[felipeweb]

any news?

[vmmusings]

@felipeweb sorry for the late reply. ss4o is based on OTEL model. Do you see anything missing over there?

[felipeweb]

Based on my understanding ss4o is not OTEL format, but is the best data model for OTEL to be stored in Opensearch. I already changed my opensearch consumer apps to search based in ss4o format.