Map OTLP HTTP request and response headers

[stevejgordon]

Per the OTel semantic conventions, client and server HTTP spans may send the request and response headers using the following attributes:

• http.request.header.<key>
• http.response.header.<key>

We don't currently map these in traces.go onto the modelpb.HTTPRequest.Headers and modelpb.HTTPResponse.Headers. As a result, if these are included in the span attributes, they are mapped onto labels.* which is not ideal.

These should ideally be mapped to our APM model.

[simitt]

@stevejgordon any chance you could pick this up at some time?

[stevejgordon]

@simitt I'd like to try to tackle this. It won't be earlier than next week, though, as I have some other competing work items.

[simitt]

@stevejgordon do you still plan to tackle this for 8.16.0?

[stevejgordon]

@simitt Unfortunately, other priorities in the agent have kept me from getting to this. I probably won't have time in the next few weeks, so if someone else can tackle it, it would be great to have it in for 8.16. Otherwise, I can try to get to it sometime in mid-late October.

[simitt]

got it, I believe we need to push it out in this case.

[dloiacono]

@stevejgordon Is it possible to solve this by modifying the corresponding APM index template?

[stevejgordon]

@dloiacono I'm not sure. Most other fixes have happened in mappings defined here.