# Integration Elastic Common Scheme with Elastic APM events intake API

**URL:** https://discuss.elastic.co/t/integration-elastic-common-scheme-with-elastic-apm-events-intake-api/363124
**Category:** APM
**Tags:** dotnet
**Created:** [July 15, 2024, 7:44am UTC](https://discuss.elastic.co/t/integration-elastic-common-scheme-with-elastic-apm-events-intake-api/363124 "2024-07-15T07:44:30Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![monty241](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/monty241/32/81681_2.png) [@monty241](https://discuss.elastic.co/u/monty241)
#### Post date: [July 15, 2024, 7:44am UTC](https://discuss.elastic.co/t/integration-elastic-common-scheme-with-elastic-apm-events-intake-api/363124/1 "2024-07-15T07:44:30Z")

</div>

The transaction schema for Elastic APM events is described on:

> **[Transactions | Elastic Observability \[8.14\] | Elastic](https://www.elastic.co/guide/en/observability/current/apm-api-transaction.html)**

However, it considerably deviates from the Elastic Common Scheme on [HTTP Fields | Elastic Common Schema (ECS) Reference [8.11] | Elastic](https://www.elastic.co/guide/en/ecs/current/ecs-http.html).

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)?