From 08a71496a533e5a2e4baaeb0b991741b1313de66 Mon Sep 17 00:00:00 2001 From: Gregor Zeitlinger Date: Tue, 12 Nov 2024 09:59:35 +0100 Subject: [PATCH] Update specification/protocol/file-exporter.md Co-authored-by: Cyrille Le Clerc --- 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 3c926742e7d..a60cce1539f 100644 --- a/specification/protocol/file-exporter.md +++ b/specification/protocol/file-exporter.md @@ -32,7 +32,7 @@ Why do we need a file exporter - why not just use the OTLP exporter? 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, which needs manual configuration and is error-prone. -- *Reliability*: Writing to a file is more reliable than sending data over the network. +- *Reliability*: Some prefer writing logs to a file rather than sending data over the network for reliability reasons. ## Exporter configuration