Skip to content
This repository was archived by the owner on Dec 6, 2024. It is now read-only.

Commit 0d0211a

Browse files
Rewrap markdown to ease commenting
1 parent 2edb609 commit 0d0211a

File tree

1 file changed

+16
-3
lines changed

1 file changed

+16
-3
lines changed

text/0199-support-elastic-common-schema-in-opentelemetry.md

+16-3
Original file line numberDiff line numberDiff line change
@@ -238,8 +238,15 @@ As the markdown code of the tables is hard to read and maintain with very long l
238238

239239
### Example an OpenTelemetry Collector Receiver to collect the access logs of a web server
240240

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
243+
[HTTP calls](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.9.0/specification/trace/semantic_conventions/http.md),
244+
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.
243250

244251
## Alternatives / Discussion
245252

@@ -257,4 +264,10 @@ Prometheus' conventions are restricted to the style of the name of the metrics (
257264

258265
## Other areas that need to be addressed by OTel (the project)
259266

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

Comments
 (0)