Steve Gordon

@martinjt I still `StringBuilder` used in the propagators. I've addressed one of these in a new PR. If that approach looks good, I can take a pass over the others.

Thanks for raising this and including the repro @ben-wallis. We'll take a look at amending the logic to account for this.

@sjrules On the Elastic backend, we receive OTLP data and map/transform it to the Elastic APM data model. We have a bunch of mappings for the semantic convention attributes, etc....

@sjrules I discussed this internally on my return from vacation, and we agree that `http.request.header.` and `http.response.header.` attributes should be mapped to our data model. I've [opened an issue](https://github.com/elastic/apm-data/issues/285) to...

@vishweshbankwar I think we can probably close this issue here since it's something we need to solve on the Elastic end and not an issue with the OTel SDK.

I'm not entirely sure why `markdownlint` fails on the autogenerated tables.

> Have you run both `attribute-registry-generation` and `table-generation`? I thought I had done so as the contents were updated, but I can try those again. I'm having to hack around...

@trisch-me I've updated the formatting per your suggestion and rerun both of those make targets. Neither made any changes to the markdown files.

Thanks, @trisch-me. Looks good!

@noahfalk / @lmolkova - I've returned to the office and updated some core changes discussed above. - clr.* is now dotnet.* - filenames are updated to align with the clr...