To ease the transition between ECS and OpenTelemetry semantic convention (SemConv) mappings, we're planning to store the two different types of data in different data streams. With the help of alias fields, we'd like to make it possible to re-use existing queries that target ECS fields on OTel data streams. Similarly, we want to add SemConv aliases to ECS-based data streams so the queries in our own UIs and in custom dashboards can target SemConv data while still making it possible to incorporate data from ECS-based data streams.
More on how we'd like to map OTel data in this PR: #104455.
One of the challenges is this requirement of alias fields:
The target field must exist at the time the alias is created.
We'd like to move away from explicitly defining fields in the mapping and instead rely on dynamic templates (such as ecs@mappings, so that the mappings only contain fields that are actually used.
However, this is incompatible with the requirement that the target for alias fields must already exist.
cc @dakrone
To ease the transition between ECS and OpenTelemetry semantic convention (SemConv) mappings, we're planning to store the two different types of data in different data streams. With the help of alias fields, we'd like to make it possible to re-use existing queries that target ECS fields on OTel data streams. Similarly, we want to add SemConv aliases to ECS-based data streams so the queries in our own UIs and in custom dashboards can target SemConv data while still making it possible to incorporate data from ECS-based data streams.
More on how we'd like to map OTel data in this PR: #104455.
One of the challenges is this requirement of alias fields:
We'd like to move away from explicitly defining fields in the mapping and instead rely on dynamic templates (such as
ecs@mappings, so that the mappings only contain fields that are actually used.However, this is incompatible with the requirement that the target for alias fields must already exist.
cc @dakrone