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
{{ message }}
This repository was archived by the owner on Dec 6, 2024. It is now read-only.
Copy file name to clipboardexpand all lines: text/0199-support-elastic-common-schema-in-opentelemetry.md
+16-3
Original file line number
Diff line number
Diff line change
@@ -238,8 +238,15 @@ As the markdown code of the tables is hard to read and maintain with very long l
238
238
239
239
### Example an OpenTelemetry Collector Receiver to collect the access logs of a web server
240
240
241
-
The author of the "OTel Collector Access logs file receiver for web server XXX" would find in the OTel Semantic Convention specifications all the guidance to map the fields of the web server logs, not only the attributes that the OTel Semantic Conventions has specified today for [HTTP calls](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.9.0/specification/trace/semantic_conventions/http.md), but also attributes for the [User Agent](https://www.elastic.co/guide/en/ecs/current/ecs-user_agent.html) or the [Geo Data](https://www.elastic.co/guide/en/ecs/current/ecs-geo.html).
242
-
This completeness of the mapping will help the author of the integration to produce OTel Log Message that will be compatible with access logs other web components (web servers, load balancers, L7 firewalls...) allowing turnkey integration with observability solutions and enabling richer correlations.
241
+
The author of the "OTel Collector Access logs file receiver for web server XXX" would find in the OTel Semantic Convention specifications all
242
+
the guidance to map the fields of the web server logs, not only the attributes that the OTel Semantic Conventions has specified today for
but also attributes for the [User Agent](https://www.elastic.co/guide/en/ecs/current/ecs-user_agent.html)
245
+
or the [Geo Data](https://www.elastic.co/guide/en/ecs/current/ecs-geo.html).
246
+
247
+
This completeness of the mapping will help the author of the integration to produce OTel Log Message that will be compatible with access logs
248
+
of other web components (web servers, load balancers, L7 firewalls...) allowing turnkey integration with observability solutions
249
+
and enabling richer correlations.
243
250
244
251
## Alternatives / Discussion
245
252
@@ -257,4 +264,10 @@ Prometheus' conventions are restricted to the style of the name of the metrics (
257
264
258
265
## Other areas that need to be addressed by OTel (the project)
259
266
260
-
Some areas that need to be addressed in the long run as ECS is integrated into OTel include defining the innovation process, providing maintainer rights to Elastic contributors who maintain ECS today, ensuring the OTel specification incorporates the changes to accommodate ECS, and a process for handling breaking changes if any (the proposal [Define semantic conventions and instrumentation stability #2180](https://github.com/open-telemetry/opentelemetry-specification/pull/2180) should tackle this point). Also, migration of existing naming (e.g. Prometheus exporter) to standardized convention (see [Semantic Conventions for System Metrics](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/system-metrics.md) , [Semantic Conventions for OS Process Metrics](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/process-metrics.md)).
267
+
Some areas that need to be addressed in the long run as ECS is integrated into OTel include defining the innovation process,
268
+
providing maintainer rights to Elastic contributors who maintain ECS today, ensuring the OTel specification incorporates the changes to
269
+
accommodate ECS, and a process for handling breaking changes if any (the proposal
270
+
[Define semantic conventions and instrumentation stability #2180](https://github.com/open-telemetry/opentelemetry-specification/pull/2180)
271
+
should tackle this point). Also, migration of existing naming (e.g. Prometheus exporter) to standardized convention (see
272
+
[Semantic Conventions for System Metrics](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/system-metrics.md) ,
273
+
[Semantic Conventions for OS Process Metrics](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/process-metrics.md)).
0 commit comments