The transaction schema for Elastic APM events is described on:
However, it considerably deviates from the Elastic Common Scheme on HTTP Fields | Elastic Common Schema (ECS) Reference [8.11] | Elastic.
For instance, for Request there is no seemingly logical way to store what would be in http.request.id in ECS. This makes correlation harder, as well as takes additional staff training time.
Is there a recommended way to map ECS to the transaction schema (and maybe even documented)?