From ca6b2fc9262ff9c597c6cd77d81d20562b316cdc Mon Sep 17 00:00:00 2001 From: Patrice Chalin Date: Thu, 16 Jan 2025 11:32:58 -0500 Subject: [PATCH] [editorial] Fix FaaS capitalization (#4369) --- specification/protocol/file-exporter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/protocol/file-exporter.md b/specification/protocol/file-exporter.md index 633a85254a1..5b04a026552 100644 --- a/specification/protocol/file-exporter.md +++ b/specification/protocol/file-exporter.md @@ -27,7 +27,7 @@ Currently, it only describes the serialization of OpenTelemetry data to the OTLP Why do we need a file exporter - why not just use the OTLP exporter? -- *Faas*: In a FaaS environment, the OTLP exporter may not be able to send data to a collector. +- *FaaS*: In a FaaS environment, the OTLP exporter may not be able to send data to a collector. - *Consistent log scraping from pods*: In a Kubernetes environment, logs are often scraped from the stdout pod file. This exporter can be used to write logs to stdout - which makes it easier to integrate with existing log scraping tools. Existing solutions add metadata, such as the trace ID, to the log line,