You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://github.com/elastic/opentelemetry-lib/enrichments implements enrichment of OTel datamodel with attributes required for APM - similar to what we do in APM data. The opentelemetry-lib implementation removes dependency from some of the old semconv and Jaeger which could help us to eliminate some of the tech debt. The enrichment currently only works for traces but opentelemetry-lib could be easily extended to metrics and logs.
In addition to enrichments, we would also need translation of OTel attributes to Elastic APM attributes in opentelemetry-lib. These mappings are already captured in otel-data plugin and would need to be coded, probably in the opentelemetry-lib itself.
To bring the changes to apm-data, the code flow would need to be modified. Instead of translating the OTel data model to APM data model and applying enrichments, we would apply enrichment and then translate to APM data model.
Note that the changes done here will also impact MIS.
WIP: document exact differences between APM data handling and opentelemetry-lib handling
The text was updated successfully, but these errors were encountered:
moving this from it105 to it106 as it's marked for 9.0, is this correct @lahsivjar ?
Yes, this sounds right. Introducing opentelemetry-lib would be breaking in some sense as the library drops some of the handling or deprecated attributes done in apm-data.
https://github.com/elastic/opentelemetry-lib/enrichments implements enrichment of OTel datamodel with attributes required for APM - similar to what we do in APM data. The opentelemetry-lib implementation removes dependency from some of the old semconv and Jaeger which could help us to eliminate some of the tech debt. The enrichment currently only works for traces but opentelemetry-lib could be easily extended to metrics and logs.
In addition to enrichments, we would also need translation of OTel attributes to Elastic APM attributes in opentelemetry-lib. These mappings are already captured in otel-data plugin and would need to be coded, probably in the opentelemetry-lib itself.
To bring the changes to apm-data, the code flow would need to be modified. Instead of translating the OTel data model to APM data model and applying enrichments, we would apply enrichment and then translate to APM data model.
Note that the changes done here will also impact MIS.
WIP: document exact differences between APM data handling and opentelemetry-lib handling
The text was updated successfully, but these errors were encountered: