Some of these attributes are defined by the OpenTelemetry Semantic Conventions: https://github.com/open-telemetry/semantic-conventions/tree/main/model/http

Would it be feasible to fix the opensearch mappings instead?

I know that some of these are in the semantic conventions, but I believe Envoy doesn't send them correctly. I didn't find a good reference configuration and don't know a way to fix these in the Envoy configuration. We can add these attributes back when we get them working.

I don't see how we could fix this with the OpenSearch mapping because the batch processor also shows the same problem.

I don't see how we could fix this with the OpenSearch mapping because the batch processor also shows the same problem.

The error is shown in the batch processor because is the error propagated by the OpenSearch exporter, see https://github.com/open-telemetry/opentelemetry-collector/blob/main/processor/batchprocessor/batch_processor.go#L263

OK, I didn't realize this is only opensearch related. I wonder why the automatic mappings are not enough.
https://opensearch.org/docs/latest/field-types/

OK, I didn't realize this is only opensearch related. I wonder why the automatic mappings are not enough. https://opensearch.org/docs/latest/field-types/

Not sure, I am not very familiar with OpenSearch. Have you tried removing the corresponding index? (maybe the http.connection.id mapping was created with some other data)

OK, I didn't realize this is only opensearch related. I wonder why the automatic mappings are not enough. https://opensearch.org/docs/latest/field-types/

Not sure, I am not very familiar with OpenSearch. Have you tried removing the corresponding index? (maybe the http.connection.id mapping was created with some other data)

I ran docker system prune -a and started a clean environment and got the problem almost right away. Are you not seeing the same problem?

OK, I didn't realize this is only opensearch related. I wonder why the automatic mappings are not enough. https://opensearch.org/docs/latest/field-types/

Not sure, I am not very familiar with OpenSearch. Have you tried removing the corresponding index? (maybe the http.connection.id mapping was created with some other data)

I ran docker system prune -a and started a clean environment and got the problem almost right away. Are you not seeing the same problem?

Not on my environment, just tested with nightly DEMO_VERSION=nightly-12898327927 and collector logs are clear.